write_bulk

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

The description adds real behavioral context beyond the annotations: Id-based upsert semantics and the all-or-nothing validation guarantee ('nothing is sent if any item is invalid'). The annotations already signal destructive and non-read-only behavior, and the description does not contradict them, though it doesn't disclose post-validation partial-failure behavior.

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?

Two sentences, with the primary action and limit front-loaded in the first sentence and the key behavioral rule in the second. No filler, no repetition of schema-visible details.

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?

The description covers resource choice, item semantics, batch limit, and initial validation, so an agent can invoke the tool. However, there is no output schema and no mention of what the call returns, and there is no detail on failure behavior after validation or an explanation of 'layer 1,' leaving gaps for a bulk mutation tool.

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 only 50%: 'resource' is described, but 'items' has no attached description. The description compensates by explaining that items with 'Id' update and items without create, plus the 500-item cap and validation behavior. This adds meaningful semantics beyond the bare JSON 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 states a specific verb ('Create or update'), a bounded resource scope ('up to 500 entities of one resource'), and the one-call bulk nature. This is clear, though 'layer 1' is unexplained and the description does not name sibling tools to explicitly distinguish itself from single-entity write operations.

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?

Bulk usage is implied by 'up to 500 entities of one resource in one call,' which suggests when this tool is appropriate, but there is no explicit guidance on when to prefer it over write_create, write_update, or other write siblings. No when-not-to-use conditions or alternatives are named.

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