Queue approved publish batch

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds valuable behavioral context: 'capacity-full items are deferred for an exact retry,' which is not covered by annotations. This explains a key non-obvious behavior, though it doesn't fully clarify retry semantics.

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 a single, front-loaded sentence that captures the core action and a key exception. Every word earns its place with no redundancy.

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 rich schema (100% parameter coverage) and presence of output schema, the description covers the primary action and the notable capacity behavior. Some ambiguity remains about the meaning of 'exact retry' and workflow placement, but overall it is sufficient for a queue 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% with detailed descriptions for approvals and timeout_ms. The tool description adds no extra parameter-level meaning, so the baseline of 3 applies.

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's function: 'Queue up to 20 approvals' with a specific resource (publish approvals) implied by the title and sibling context. It distinguishes from sibling 'queue_publish_job' by the batch nature (up to 20). The verb 'Queue' is specific and the scope is clear.

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 implies usage for batch queueing (up to 20 approvals) but does not explicitly state when to use this instead of alternatives like queue_publish_job. No exclusions or alternative guidance is provided, so usage is only implicitly conveyed.

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