Get Cost Item

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns 'full details' and includes the API endpoint, which provides mild behavioral context. No contradictions, but little extra 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?

Description has 4 sentences. It is reasonably concise but includes redundant opening 'Get Cost Item' that mirrors the tool name. The endpoint information is helpful but adds length. Overall, it is adequately structured but could be more front-loaded.

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 read-only fetch tool with well-documented parameters, the description covers the basic function. However, it lacks details on the response format (beyond 'JSON object describing ...') and does not address error cases or missing items. With no output schema, more completeness would be helpful.

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?

Schema description coverage is 100%, so baseline is 3. The description restates required parameters but adds no additional meaning beyond the schema. The page and per_page parameters are not mentioned in the description.

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 'fetch the full details of a specific Cost Catalog records by its identifier', specifying the verb (fetch) and resource (Cost Catalog record). It distinguishes from sibling 'get_cost_items' by focusing on a single item via identifier.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_cost_items' (list) or 'update_cost_item'. The description only lists required parameters but does not clarify the tool's appropriate context or exclusions. This forces the agent to infer usage from the tool name.

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