List All Direct Cost Line Items

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds context about pagination (page, per_page, metadata) and filtering capabilities, which are not covered by 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?

The description is relatively concise with front-loaded purpose. It includes a helpful link to filtering docs. However, it has minor redundancy ('Return a list' and 'Returns a paginated JSON array') that could be trimmed.

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 tool with 9 parameters and no output schema, the description covers basic usage (pagination, filtering) and links to external docs. But it does not fully explain the response structure beyond 'paginated JSON array of Direct Costs', leaving some ambiguity. An output schema would help.

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?

All parameters are fully described in the input schema (100% coverage). The description reiterates required parameter and pagination, but does not add significant new meaning beyond the schema. Baseline 3 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 a list of Direct Cost Line Items, with specific verb 'Return a list' and resource. It mentions use cases like paginated overview and filtering. However, it does not differentiate from the sibling 'list_direct_cost_items', which has a similar name and purpose.

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 advises when to use the tool (enumerate, find IDs, filter) and mentions pagination control. But it lacks explicit guidance on when not to use it or alternatives (e.g., when a single item is needed or when to use 'list_direct_cost_items' instead).

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