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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds access-control context: the queue is admin-only and contains private disputed reports. This is useful, but it does not disclose how authentication works or what the returned queue contains beyond 'disputed reports.'

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 very concise and front-loads the key scope: admin-only and private disputed reports. It has no filler, though it is terse enough to omit a verb and any invocation or selection cues.

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?

This is a read-only queue with no output schema, so the description should clarify invocation prerequisites and return content. It does not mention the admin_token requirement, what fields or reports appear in the queue, or how this tool relates to sibling admin dispute actions. Annotations cover safety but not call completeness.

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 schema documents agent_key well but leaves admin_token with only a minLength constraint and no description. The description mentions neither parameter, so with only 50% schema coverage an agent cannot understand how admin_token is issued or how it relates to agent_key.

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 identifies a specific resource: an admin-only queue of private disputed reports. This distinguishes it from sibling admin actions like resolve_dispute or approve, but it is a noun phrase rather than an explicit verb, so the retrieval action is implied.

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 is provided about when to call this tool versus its many admin siblings. 'Admin-only' is the only contextual signal, but it does not help an agent choose between this, resolve_dispute, reconciliation, or other exchange_funded_task_admin_* tools.

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