List Direct Cost Items

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

The description discloses behavioral traits beyond annotations, such as pagination via page/per_page and filtering capabilities. Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description adds operational context 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 front-loaded and relatively concise, but it redundantly states 'Returns a list' and 'Returns a paginated JSON array'. Still, essential information is presented without unnecessary fluff.

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 simple list tool with complete schema coverage and annotations, the description adequately covers purpose, usage, pagination, and required parameters. It lacks output structure details but no output schema exists.

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 the description adds minimal parameter semantics beyond mentioning project_id as required and page/per_page for pagination. The filtering link provides extra context, but overall value is limited.

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 it returns a list of all Direct Cost Items for a Project, with specific verb and resource. However, it does not explicitly differentiate from sibling tools like list_direct_cost_line_items, which could cause confusion.

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?

Provides clear guidance: 'Use this to enumerate Direct Costs when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions pagination controls. However, it does not explicitly state when not to use or suggest alternatives.

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