Get Cost Items

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral details: pagination control via page and per_page, and that the response includes pagination metadata. This provides sufficient context beyond the annotations without contradiction.

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 concise (3 sentences + endpoint info), front-loads the main purpose, and avoids fluff. Every sentence adds necessary information about purpose, usage, pagination, and required parameters.

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?

For a list endpoint with 6 parameters, annotations, and no output schema, the description is fairly complete. It covers pagination, required parameters, and the general return type. It could benefit from detailing the structure of a 'Cost Catalog record', but the endpoint documentation is referenced.

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?

Input schema has 100% coverage for all 6 parameters. The description adds value by noting that page and per_page control pagination, supplementing the schema's default and max values. It also restates required parameters, which is helpful for quick reference.

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 cost items for a specific catalog, using the verb 'Returns' and identifying the resource as 'Cost Items for a Catalog'. It distinguishes from sibling tools like 'get_cost_item' (singular) by implying a list operation, and from 'get_catalogs' by specifying 'items'.

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 provides context for when to use the tool ('Use this to fetch the full details of a specific Cost Catalog records by its identifier'). However, it does not explicitly mention when not to use it or include alternatives like 'get_cost_item' for a single item, leaving room for ambiguity.

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