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

Annotations are minimal (only readOnlyHint, openWorldHint, idempotentHint, destructiveHint), so the description carries the full burden. It discloses failure modes (payment_required, quota_exceeded), per-entry error containment in results, and the idempotency behavior nuance (generated when omitted makes batch NOT safe to resend). This goes well beyond annotations and gives the agent accurate expectations.

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 compact yet richly informative: front-loaded purpose, then usage conditions, then output and failure summary. Every sentence earns its place, with no fluff or redundancy. Formatting with line breaks improves scanability.

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 return fields (created_count, existing_count, failed_count, results, headroom), failure modes, prerequisite quota check, and idempotency guidance. No output schema exists, so this self-contained description is complete for an agent to call correctly. It addresses all critical aspects for a batch write operation.

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% and the schema itself explains each field thoroughly, including the idempotency_key caveat. The description adds only a usage-style hint about supplying a key when resending, which is already implied by the schema. No new parameter semantics are added beyond what the schema provides, so a 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 verb and resource: 'Publish several pins in one call' with per-entry outcomes. It explicitly distinguishes from create_pin by instructing 'otherwise call create_pin per pin', making it unmistakable which tool to select for bulk 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?

Provides explicit when-to-use conditions: 'Use for bulk publishing (up to 100 pins) when the workspace has the bulk_imports feature; otherwise call create_pin per pin.' It also adds a prerequisite: 'Check get_billing_status for quota first' and advises on idempotency_key usage. This leaves no ambiguity about alternatives or prerequisites.

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