List whispers awaiting an answer

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuine lifecycle semantics beyond them: ordering is oldest-first, a whisper leaves the list once answered, and deferred observations never appear because they raised no whisper. No mention of pagination or result size limits, so not quite a 5.

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?

Front-loaded with the action and scope, then usage routing, then edge-case behavior, then the parameter note. Every sentence carries information; there is no filler.

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?

An output schema exists, so return values need not be described. For a single-optional-param, read-only list tool the description covers purpose, routing, lifecycle edge cases, and filter semantics completely.

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 100%, so the baseline is 3, but the description adds real meaning: the worker filter matches 'the exact URI given to submit_observation', clarifying exact-match semantics rather than a fuzzy name lookup.

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?

States a specific verb and resource ('List the whispers still waiting for a worker's answer'), plus scope details (oldest first, one call). An agent can distinguish it from answer_whisper and submit_observation without opening the schema.

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?

Explicitly states when to use it (recover a whisper_id before relaying an answer) and when not to (submit_observation already returns the whisper_id, so call this only when you no longer have it). This is a textbook when/when-not plus alternative routing.

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