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

With no annotations provided, the description must carry behavioral weight, and it does add useful context: it restricts results to disputes assigned to the caller as arbiter and states the ordering. However, it does not explicitly state that the operation is read-only, clarify what 'drawn' means, or describe edge behavior such as an empty inbox or whether only unresolved disputes are included.

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 first sentence is reasonably tight, but the second sentence, 'The inbox a drawn arbiter was missing,' is ungrammatical, vague, and adds no operational value. It undermines the otherwise compact description rather than contributing useful guidance.

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?

Given no annotations, no output schema, and an undocumented required parameter, the description is incomplete for reliable invocation. It covers scope and ordering but leaves the agent uncertain about how to populate the 'arbiter' parameter, what the response looks like, and what behavioral guarantees apply.

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 0% and the description never mentions the required 'arbiter' parameter. The phrase 'drawn to you as arbiter' obliquely suggests the arbiter is the caller, but it does not clarify whether the caller must pass their own arbiter ID or can filter by another arbiter, which is a significant ambiguity for a required parameter.

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 ('disputes drawn to you as arbiter') and a concrete behavior (oldest deadline first), which makes the tool's purpose reasonably clear. The verb 'Open' is slightly ambiguous—it could mean 'list open disputes' rather than 'open' as an action—but the overall intent is understandable and distinguishable from generic list tools.

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 explicit when-to-use or when-not-to-use guidance is provided, and no sibling alternatives such as list_inbox, list_cases, or get_dispute are mentioned. The arbiter scope is the only contextual hint, leaving the agent to infer when this tool should be chosen over related tools.

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