morpheus-mcp

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

With no annotations provided, the description carries full disclosure burden. It reveals critical execution semantics: sequential processing and stop-on-first-failure behavior. It also documents the expected object structure (task_id, phase, evidence). It lacks rate limits or auth details, but the execution model is transparent.

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 efficiently structured in four sentences: purpose statement, execution semantics, input format specification, and Args section. Every sentence earns its place; there is no redundancy or generic filler. Information is front-loaded with the core purpose.

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 that an output schema exists (per context signals), the description appropriately omits return value details. It covers the essential complexity of a batch operation—specifically the partial failure behavior—and compensates for the barren input schema. It could mention rate limits or prerequisites, but it is sufficient for tool invocation.

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?

Schema description coverage is 0%—the 'advances' parameter has no schema description and is typed only as 'string'. The description provides essential compensation by specifying that this string must contain a 'JSON array of objects with keys: task_id, phase, evidence', without which the tool would be unusable.

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 opens with a specific verb ('Advance') and clearly identifies the resource ('multiple tasks through phase gates') and batch nature ('in a single call'). It effectively distinguishes itself from the sibling tool 'morpheus_advance' by emphasizing the batch processing capability.

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 behavioral context ('Stops at the first failure') which implicitly guides usage—warning that partial completion is possible. While it doesn't explicitly name 'morpheus_advance' as the single-task alternative, the phrase 'multiple tasks... in a single call' makes the batch use case clear relative to the singular sibling tool name.

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