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

With no annotations provided, the description carries the full burden of disclosing behavior. It contributes useful semantics: the queue is pull-based, uses leases, and timed-out leases are requeued. However, it says nothing about the creation operation's side effects, idempotency, or permission requirements, leaving important behavioral aspects undisclosed.

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, information-dense sentence. It front-loads the key concept (pull-based work queue) and adds a critical behavior (timed-out leases requeue) without wasted words. It earns a high score for conciseness, though it stops short of 5 because it omits parameter explanations that would improve its value.

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 tool with three undocumented parameters and no output schema, the description is largely incomplete. It explains the queue's behavior but leaves the practical usage (what parameters mean, what the result is, how to interact after creation) entirely unstated. The agent cannot confidently invoke this tool correctly.

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?

The schema has three parameters (days, max_attempts, lease_seconds) with 0% description coverage. The description does not mention any of them, nor does it offer hints about their purpose. Since the schema descriptions are empty, the agent has no way to understand what these parameters control.

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 describes the tool as a 'pull-based work queue with leases,' which clearly identifies the resource type. While the verb 'create' is not explicitly stated in the description, the tool name 'create_queue' makes the action evident. It lacks a direct verb, so it doesn't fully meet the 5-level criteria.

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 provides no guidance on when to use this tool relative to its siblings like queue_push, queue_lease, or other create_* tools. It doesn't mention prerequisites, competing alternatives, or exclusion criteria. The agent must infer usage from the tool name alone.

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