list_queue

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

With no annotations, the description discloses behavioral traits: statuses ('unsent', 'sent', 'no-open-access-pdf'), key uniqueness for duplicates, and UTC dates. It fully covers what the tool returns and its read-only nature.

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 sentences, each earning its place. First sentence states purpose, second lists statuses, third gives usage and key details, fourth mentions dates. No waste.

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 no params and an output schema (not shown), the description sufficiently explains return fields and behavior. It covers purpose, usage, statuses, keys, and dates, making it complete for a listing tool.

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?

No parameters exist, so schema coverage is irrelevant. Description adds no parameter info, but baseline is 4 since there are no parameters to describe.

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 explicitly states it lists the reading queue with delivery status per item. It distinguishes from siblings by mentioning usage before send_queue and for remove_from_queue, and highlights unique key and date fields.

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?

It provides explicit guidance: 'Use this to show the user their queue, before send_queue ... or to find refs for remove_from_queue.' This tells when to use this tool versus alternatives like send_queue or remove_from_queue.

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