list_pending

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses pagination with a 1.5s pause, reveals that both 'pending' and 'unknown' entries are returned (fail-closed), and explicitly warns that 'unknown' entries require manual review before any automatic response. This is strong, risk-relevant behavioral disclosure.

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 compact and front-loaded: purpose first, then pagination behavior, then output categories and a high-visibility warning. Every sentence earns its place, and the warning is highlighted appropriately without excessive length.

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 list tool with no output schema, the description covers the essential context: what counts as pending, pagination behavior, category semantics, and a manual-review warning. It does not specify the shape of individual returned entries or authentication prerequisites, but those are less critical for a read-oriented listing operation and are partially implied by the sibling toolset.

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%, so the parameter meanings are already fully documented. The description adds no new parameter-level semantics; it only reinforces the existing schema explanations. Baseline 3 is appropriate because the schema does the heavy lifting.

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 purpose: it searches for conversations pending a response, and precisely defines 'pending' as the last message being from the other party rather than the user. This specific verb-plus-resource framing makes the tool's scope unmistakable and distinguishes it from the broader sibling list_conversations.

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?

Usage is implied rather than explicit: the description implies you would call this tool when you need pending conversations, but it never names alternatives or states when NOT to use it. Given siblings like list_conversations, get_conversation, and get_counters, explicit routing guidance would have been valuable.

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