morpheus-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully indicates the tool performs a state-changing completion action and returns a summary. However, it lacks details on side effects (e.g., whether the plan becomes read-only), idempotency, or error conditions.

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 exceptionally concise with two front-loaded sentences. The first states purpose and return value; the second documents the parameter. There is no redundant or wasted text.

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 tool's simplicity (1 parameter) and existence of an output schema, the description is reasonably complete. It appropriately mentions the return value ('final summary') without needing to detail the schema structure. However, with 9 sibling tools, slightly more lifecycle positioning would strengthen 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?

The schema has 0% description coverage. The description compensates by documenting the single parameter in the Args section ('The plan ID to close'), providing basic semantic meaning. However, it omits format details, constraints, or where to obtain the plan_id.

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 marks a plan as 'completed' and returns a 'final summary', using specific verbs and identifying the resource. The 'completed' and 'final' language effectively signals this is a terminal lifecycle operation, distinguishing it from siblings like morpheus_init or morpheus_advance without needing to explicitly name them.

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 implies usage context through 'completed' and 'final summary', suggesting this is the last step in a workflow. However, it lacks explicit guidance on when to prefer this over morpheus_advance or prerequisites for closing.

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