List Direct Cost Line Items

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds valuable behavioral context: pagination with page/per_page, pagination metadata, and required parameters. No contradictions with 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 is brief (4 sentences), front-loaded with main purpose. Includes a helpful link to filtering documentation. No redundancy or fluff. Efficient and structured.

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?

No output schema is provided, so description should compensate. It states returns a paginated JSON array of Direct Costs with pagination metadata. However, it does not describe the fields of each line item, limiting utility. Adequate but not detailed.

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%, so baseline 3. Description adds meaning by highlighting required parameters (project_id, direct_cost_id) and role of page/per_page for pagination. It mentions filtering capability via link, but does not detail each filter. Adds moderate value beyond schema.

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 Direct Cost Line Items, specifies usage for enumeration, ID finding, and filtering. Minor inconsistency: says 'Direct Costs' instead of 'line items' in one place. Does not explicitly differentiate from the sibling 'list_all_direct_cost_line_items' but overall purpose is clear.

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 explicit usage scenarios: paginated overview, finding IDs, filtering. However, it does not state when to avoid this tool or mention alternatives like 'list_all_direct_cost_line_items'. Includes a filtering documentation link, but lacks exclusions.

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