List Project Cost Codes

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds that it returns a paginated JSON array with pagination metadata, and details on controlling pagination with page/per_page. 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?

The description is concise with exactly 5 sentences, each serving a distinct purpose: purpose, usage, return format, pagination control, and API reference. No unnecessary words.

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 no output schema, the description includes return format (paginated JSON array) and API endpoint details. It could explain the structure of each Directory record but is sufficiently complete for a list tool with clear purpose.

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 has 100% coverage for 3 parameters. Description mentions required project_id and guidance on page/per_page for pagination, which adds some context but does not significantly enhance 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 states it returns a distinct list of cost codes in use on vendors for a given project, with a specific verb and resource. However, it later mentions 'Directory records' which is slightly inconsistent but the core purpose remains 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?

The description provides when to use the tool (enumerate Directory records with pagination, find IDs, filter). It does not specify when not to use or offer alternative tools among many sibling list functions.

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