morpheus-mcp

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

No annotations provided, so description carries full burden. It discloses the mutation effect ('Clears any oil_change_due advisory') and the prerequisite relationship with sentinel_health_check. Missing explicit statements on idempotency or error states, but covers the primary behavioral traits.

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?

Three tight sentences followed by a structured Args block. No filler text. Information is front-loaded (action, workflow, effect) before parameter details. Every sentence earns its place.

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 output schema exists (per context signals), the description appropriately omits return value details. It covers the action, workflow context, side effects, and all undocumented parameters. Minor gap: could mention what happens if health_check_id is invalid, but sufficient for selection.

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% (titles only), but the description compensates perfectly via the 'Args:' block. It documents all 3 parameters with specific semantics: health_check_id is linked to sentinel_health_check results, and commits_since_last clarifies the temporal reference ('since last health check').

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?

States specific action ('Record an oil change') and resource ('plan'), with the metaphor explained as a 'macro-lens health check'. Describes the side effect (clears advisory). However, it does not explicitly differentiate from sibling morpheus tools (e.g., how this differs from morpheus_status or morpheus_reflect).

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?

Provides explicit workflow guidance: 'Call this after running sentinel_health_check and reviewing the results.' This establishes clear prerequisites and temporal ordering, telling the agent exactly when to invoke the tool vs. its dependency.

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