List All Project Budgeted Production Quantities

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that the response is a paginated JSON array with metadata, which annotations do not cover. There is no contradiction; the description aligns 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 4 sentences, front-loaded with purpose, and structured logically: purpose, use cases, parameters, and additional context like API endpoint. No wasted 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 the low complexity of a list tool with well-annotated schema and annotations, the description is fully adequate. It explains the return type (paginated JSON array), mentions pagination metadata, and includes Procore API reference for additional context. No gaps detected.

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 the baseline is 3. The description mentions required project_id and pagination parameters (page, per_page) but adds minimal value beyond the schema, as the schema already includes full descriptions for all parameters.

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 Budgeted Production Quantities for a specified project, using specific verb 'Return a list'. It distinguishes from siblings like the IDs-only endpoint by mentioning 'to find IDs' and providing pagination details.

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 explicitly states when to use: to enumerate records for paginated overview, find IDs, or filter by query parameters. It mentions pagination control but does not explicitly exclude use cases or list alternatives, though the sibling list provides implicit contrast.

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