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

With no annotations, the description carries the behavioral disclosure burden. It does disclose consumption, FIFO order, and the empty-queue null return. However, it does not say whether the item is permanently removed or leased, whether acknowledgment is required, or how errors like a missing queue are handled—gaps that matter given queue_ack, queue_nack, and queue_receipt_status siblings.

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, front-loaded with the verb, resource, and ordering guarantee. Every sentence earns its place: one defines the action, one gives usage context and the empty-queue result. No filler or redundant restatement.

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?

There is no output schema, so the description must explain what a successful call returns, but it only covers the empty case. It also omits the ack/nack lifecycle and whether this operation removes or leases the item. For a consuming tool with no annotations, that leaves an agent uncertain about side effects and follow-up calls.

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 33%, and the description does not compensate. The required name and slug parameters have no descriptions, and while 'named queue' hints that name identifies the queue, slug is left unexplained and the relationship between name and slug is unclear. The optional owner_key is the only parameter with actual schema documentation.

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 names a specific verb (fetch/consume), a specific resource (a named queue), and an ordering guarantee (FIFO, oldest visible item). It also distinguishes itself from queue_pop by stating they behave the same and references queue_list_items, so an agent can tell this apart from sibling queue tools.

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 gives concrete context: use this after queue_list_items or after finding the right queue. It names queue_pop as a same-behavior alternative but does not explain when to prefer one over the other, so the exclusion guidance is incomplete.

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