morpheus-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. While 'Get' implies a read-only operation, the description does not explicitly confirm safety, idempotency, or side effects. It explains what data is returned but lacks behavioral traits beyond the operation type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with the purpose front-loaded, followed by default behavior and an Args section. There is slight redundancy between the prose explanation of plan_id and the Args section, but every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown but indicated), the description appropriately omits return value details. It covers the essential operational context for a single-parameter status tool, though sibling differentiation would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates effectively by explaining that plan_id defaults to the most recent plan when omitted. This semantic explanation of the null/default value is crucial and not inferable from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves 'current plan progress, task states, and active phase' using specific verbs and resources. However, it does not differentiate from sibling tools like 'morpheus_progress' or 'morpheus_gate_summary' which may return similar information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on parameter usage (when plan_id is omitted), but offers no guidance on when to select this tool versus siblings like morpheus_progress or morpheus_gate_summary. Usage is implied by the name but not explicitly contextualized.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.