Bulk Create Actual Production Quantities

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

Description discloses partial failures, adding value over annotations (readOnlyHint=false, etc.). However, it does not detail performance, error handling, or side effects beyond partial failures.

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-5 sentences, starting with the action and including key points. Minor typo 'records records' slightly reduces clarity.

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 and 100% parameter coverage, the description covers partial failures and endpoint path. Lacks details on array item structure or error handling for individual items.

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?

Both parameters have schema descriptions (100% coverage). The description adds no extra meaning beyond the schema, so 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 bulk creates Actual Production Quantities, specifies it creates multiple records in a single request (HTTP 201), and includes the Procore API endpoint path. However, it could be more distinct from sibling bulk-create tools.

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 says 'Use this to create many Field Productivity records' and mentions partial failures, but lacks explicit guidance on when not to use or comparison with alternative tools like bulk_create_timecard_entries.

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