morpheus-mcp

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

No annotations provided, so description carries full burden. It implies read-only behavior via 'Return,' but does not explicitly confirm safety, idempotency, or disclose rate limits. Mentions three specific version components being returned.

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?

Two highly efficient sentences with zero waste. Front-loaded with the return value specification, followed by usage guidance. Every word 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?

Appropriate for a low-complexity tool with 0 parameters and existing output schema. Covers return values at high level and usage context. Could be strengthened by explicitly confirming read-only safety given lack of annotations.

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?

Tool has zero parameters, establishing baseline of 4. The description adds value by explicitly confirming 'No arguments required,' which aligns with the empty input schema and prevents parameter hallucination.

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 uses specific verbs ('Return') and identifies exact resources (Morpheus server version, plan schema version, Python version). It clearly distinguishes this introspection tool from operational siblings like morpheus_advance and morpheus_init.

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?

Explicitly states 'No arguments required' and provides clear usage context ('introspection and compatibility checks'). Lacks explicit 'when not to use' guidance, though this is less critical for a non-destructive metadata tool.

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