list_pending

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to restate that. It adds useful context that the results are tool calls awaiting human decisions, but it says nothing about ordering, pagination, scope across users or workspaces, or what happens when nothing is pending.

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 definition is a single, front-loaded sentence with no filler or redundant wording. It states the core behavior immediately and does not bury it in unnecessary qualifications.

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 zero-parameter read tool this is minimally adequate, especially because the readOnlyHint covers the safety profile. But with no output schema, the description should say more about what the returned list contains, how it is ordered, and how it relates to approval_status; those omissions leave real ambiguity for an agent choosing between the two.

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?

This tool has zero parameters, so there are no parameter semantics for the description to clarify. The baseline for a parameterless tool applies, and the description does not introduce any misleading parameter expectations.

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 gives a specific verb and resource: it lists tool calls awaiting a human decision. That is clear enough to separate it from ticket and customer siblings, but it does not distinguish it from approval_status, which appears to cover overlapping approval territory.

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 intended use case is implied by 'waiting for a human decision,' so an agent can infer this is for finding pending approvals. However, there is no explicit when-to-use guidance, no mention of when not to use it, and no reference to approval_status as an alternative.

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