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. It discloses key behaviors: parsing markdown, persisting to a store ('saves plan and tasks'), and returning a summary with IDs. However, it omits critical mutation details like idempotency (whether calling twice overwrites state), file existence requirements, 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 efficiently structured with a clear one-sentence purpose, a second sentence detailing the processing steps, and an Args section documenting the single parameter. No extraneous information is present.

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 has only one required parameter and an output schema exists, the description provides sufficient context. It explains the input parameter and gives a high-level summary of the return value without needing to replicate the full output schema structure.

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 (only title and type). The description compensates by specifying that plan_file is a 'Filesystem path to the plan markdown file,' clarifying both the format (markdown) and nature (filesystem path). It could be improved by noting absolute vs. relative path handling or file encoding requirements.

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 specific action ('Load a plan file'), the target system ('into Morpheus'), and the outcome ('begin tracking state'). It effectively distinguishes itself as the initialization entry point among siblings like morpheus_advance and morpheus_close.

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 phrase 'begin tracking state' implies this is the first step in the workflow, but the description lacks explicit guidance on when to use this versus other tools (e.g., 'Call this before morpheus_advance') or prerequisites (e.g., whether Morpheus must be in a specific state).

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