list_pending_followups

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

No annotations and the description discloses nothing about behavior: not whether it is read-only, whether it requires authentication, what the return looks like, pagination, or rate limits. It carries the full burden and fails.

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 single sentence is short but uninformative; it is under-specified rather than concise. The cryptic 'Extended: account queue' prefix is not front-loaded with useful information.

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 operation with one required parameter and no output schema, the description should at least explain the purpose, scope, and return type. It provides none of this, leaving the agent unable to confidently invoke the 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?

Schema coverage is 100% and the only parameter bcId is described in the schema as 'Agent bc id'. The description adds nothing beyond that, so the baseline of 3 applies.

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 'Extended: account queue (ListPendingFollowups)' does not state a clear verb+resource; it restates the internal function name and adds an opaque 'Extended' label. It gives no sense of what the tool does beyond the tool name, and does not distinguish it from siblings like create_followup_run or list_runs.

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?

No guidance on when to use this tool versus alternatives. No context about what 'pending followups' are or when the account queue should be queried.

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