Show Direct Cost Line Item

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds value by specifying it returns a JSON object and the endpoint, but does not contradict annotations. No contradictions.

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?

Four sentences, purpose front-loaded, no wasted words. Each sentence serves a distinct purpose: what it does, when to use, required params, and API source.

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 the full schema coverage and annotations, the description adequately covers all necessary context: it states a JSON object is returned, lists required params, and provides the API endpoint. No missing information.

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 coverage is 100% and the description merely lists required parameters that are already in the schema's required array. It does not add additional meaning beyond the schema descriptions.

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 'Returns detailed information on a Direct Cost Line Item' and specifies it fetches full details by identifier, distinguishing it from listing tools like 'list_all_direct_cost_line_items'. It also mentions the API endpoint method.

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?

It explicitly says 'Use this to fetch the full details of a specific Direct Costs by its identifier', providing clear when-to-use context. However, it does not mention when not to use it or differentiate from the sibling 'show_direct_cost_item'.

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