Bulk Create

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

Beyond the annotations (which only indicate non-readonly, non-destructive, non-idempotent, and open-world), the description adds important behavioral traits: max 25 entries, partial failures possible, returns the created collection, and the experimental status. This helps the agent understand side effects and error handling.

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 somewhat verbose and contains repetition (e.g., 'Creates many Field Productivity records records'). It includes essential information but could be more concise, especially by removing redundant phrases. The structure is acceptable but not optimal.

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 complexity of a bulk create tool with three required parameters and no output schema, the description covers key aspects: max limit, HTTP status on success, partial failure behavior, and required parameters. It provides sufficient context for an agent to understand the tool's behavior.

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?

The input schema covers all three parameters with descriptions, so the description adds limited extra meaning. It restates the required parameters but does not elaborate on the format of equipment_timecard_entries array beyond the schema, resulting in a baseline score of 3.

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 explicitly states it creates equipment timecard entries in a bulk transaction, specifies the max limit of 25, and mentions it returns HTTP 201. It clearly identifies the resource and action, distinguishing it from siblings by providing the specific endpoint and field productivity context.

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 explains when to use the tool (to create many Field Productivity records in one request) and notes that it is experimental and requires beta access. However, it does not explicitly state when not to use it or provide alternatives, which would help an agent choose between similar bulk create tools.

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