catalog

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

No annotations provided. Description adds value by stating 'Free' and 'live prices', indicating no cost and real-time data. Does not mention auth or side effects, but for a read-only listing this is adequate.

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 no wasted words. Front-loaded with the main action 'List every service'. Highly concise and well-structured.

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?

No output schema, but description explains what is returned (list of services with prices in KAS and USD). Also clarifies it's free and a starting point. Fully complete for a simple catalog tool.

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 in input schema, so description cannot add parameter semantics beyond what schema provides. Baseline 4 for 0 params, but description adds context about output content (services, prices in KAS/USD), earning a 5.

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?

Description clearly states the tool lists all services with live prices, using specific verb 'List every service'. Distinct from sibling tools that perform different functions like classify, embed, etc.

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 says 'Start here' to discover what's available and costs, providing clear usage context. No explicit when-not-to-use, but the guidance is sufficient for a catalog tool.

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