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

Beyond the annotations (which only flag it as a non-idempotent write), the description discloses partial-failure semantics ('each item is processed independently - one failure does not affect others'), the required write scope, and the rate-limit accounting ('counts as 1 request'). These are exactly the traits an agent needs before invoking a mutating bulk tool.

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?

Four short sentences, each carrying distinct information (batching, partial-failure behavior, return shape, auth and rate-limit cost), with the core purpose front-loaded. Zero filler.

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?

For a two-parameter, no-output-schema tool, the description compensates well by noting that per-item results are returned and that failures are isolated, plus scope and rate-limit constraints. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so both `items` and `resource` are already documented in the schema, including the max-100 bound. The description adds the `{resource}:write` scope note but no field-level or format detail beyond the schema; baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource with scope: 'Create multiple records of a resource type in one API call (max 100).' The bulk framing implicitly distinguishes it from the many single `create_*` siblings, but it never names a specific alternative, so the differentiation is inferred rather than explicit.

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 'multiple records ... in one API call' and max-100 framing imply when bulk is appropriate, but there is no explicit when-to-use rule or named alternative (e.g. 'use create_asset for a single record'). Context is present but left to the agent's inference.

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