hermesplant_api_catalog

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces 'read-only' and adds that it 'returns raw JSON text' and 'performs no paid API calls', providing extra behavioral context beyond annotations.

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 sentences with zero waste. First sentence states action and resource, second provides usage context and behavioral note. Front-loaded and efficient.

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 no parameters, rich annotations, and simple output (raw JSON text), the description covers all necessary aspects: purpose, usage context, and behavioral traits. It is fully adequate for an agent to use this tool correctly.

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?

No parameters (0 params), so schema coverage is 100%. Baseline for 0 params is 4. The description does not need to add parameter info, and it correctly omits extraneous details.

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 verb 'Fetches', the specific resource 'Hermes Plant's RFC 9727-style API catalog', and the exact location '/.well-known/api-catalog'. It lists specific contents (OpenAPI links, MCP metadata, pricing, provider contact) that distinguish it from sibling catalog tools.

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 'Use this when a client needs machine-readable service discovery, OpenAPI links, MCP metadata links, pricing metadata, and provider contact details.' While it doesn't explicitly exclude other scenarios or name alternatives, the context is clear and actionable.

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