get-catalog

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

Without annotations, the description should disclose that the tool is non-destructive. The word 'Return' implies reading, but it does not explicitly confirm safety or idempotency. No additional behavioral traits are described.

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 two sentences, clear and without unnecessary words. Every sentence adds value: the first states the action and source, the second notes the tool's purpose for other agents.

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?

The description is sufficient for a simple no-parameter read operation, but it does not explain what the catalog contains or its format. Given the lack of output schema and sibling tools, additional context about the catalog's scope would improve completeness.

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?

There are no parameters, and the schema has 100% coverage. The description does not need to add parameter details, so a baseline of 4 is appropriate.

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 tool returns the published catalog from a specific source (./catalog.json), using the verb 'Return' and specifying the resource 'published catalog'. This distinguishes it from sibling tools like 'publish-catalog' and other read 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?

The description implies this tool is for reading the catalog, but does not explicitly state when to use it versus alternatives like 'get-product' or other read-only tools. No exclusions or alternative suggestions are provided.

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