list_pending_verifications

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that only pending verifications are listed and that the results show checkpoints and votes, which adds useful context. However, it does not mention read-only nature, pagination behavior, ordering, or potential permissions needed, leaving some 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 two sentences long, front-loads the main purpose, and includes no filler or redundant information. Every word contributes to understanding the tool's function and scope.

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 simple list tool with two parameters and no output schema, the description is largely complete. It explains the purpose, the group scope, and the expected content ('checkpoints and votes'). While it could mention the limit parameter or default behavior, those are already in the schema, and the absence of an output schema is mitigated by the clear statement of what is shown.

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 input schema has 100% description coverage for both parameters (group and limit), so the schema already documents them fully. The description adds no additional meaning beyond the schema, which matches the baseline of 3 when 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 uses a specific verb ('List') and resource ('pending Human-in-the-Loop verifications') with a clear scope ('for a group'). It also distinguishes itself from sibling tools by naming 'verifications' rather than proposals or votes, and clarifies it shows 'checkpoints and votes awaiting human approval.'

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 implies when to use the tool (to see pending verifications for a group) but does not explicitly state alternatives or exclusion criteria. It does not mention cases where another tool like 'list_proposals' or 'cast_vote' would be more appropriate, leaving usage context implied rather than fully guided.

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