🟢 P2: Inconsistent argument names across tools (content vs brief_content)

[mmorris35]

Problem

Different tools use different argument names for the same concept:

• devplan_parse_brief(content: string)
• devplan_generate_plan(brief_content: string)
• devplan_validate_haiku_executable(plan_content: string)

This is confusing and causes errors when users assume consistent naming.

Reproduction

# Works
mcporter call devplan.devplan_parse_brief --args '{"content": "..."}'

# Fails - wrong arg name
mcporter call devplan.devplan_generate_plan --args '{"content": "..."}'
# Error: "brief_content" required

# Need to remember different name
mcporter call devplan.devplan_generate_plan --args '{"brief_content": "..."}'

Expected Behavior

Consistent naming:

• content for all tools taking document content, OR
• brief_content / plan_content everywhere (explicit and consistent)

Suggested Fix

Option A: Use content everywhere (simpler)
Option B: Use explicit names everywhere: brief_content, plan_content, report_content

Either is fine, but be consistent.

Impact

Low - Causes minor friction, easily discovered through error messages. But unnecessary friction for new users.