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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the kind of information returned (raiser, decider, outcome), which is useful, but it does not explicitly state that this is a read-only operation, mention error conditions, or describe side effects. The name 'get' and the content listing partially compensate.

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 a single compact sentence fragment that conveys the essential output dimensions without wasted words. It is not a full sentence, but it is front-loaded and scannable.

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 single-parameter getter, the description covers the return content but omits usage context relative to sibling dispute tools and does not explicitly confirm read-only behavior. With no output schema or annotations, a bit more context about what the agent should expect would improve 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?

Schema description coverage is 0%, and the description does not mention taskId at all. The parameter name is self-explanatory, but the description provides no additional meaning about the expected format, semantics, or relationship to disputes.

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 the resource as 'the dispute on a task' and specifies the dimensions it covers: who raised it, who decides, and what came of it. This clearly differentiates it from list_disputes (plural listing), raise_dispute (creation), and arbitrate_dispute (resolution), though it never explicitly states a verb like 'retrieves'.

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 given for when to use this tool versus the closely related siblings such as list_disputes, raise_dispute, or arbitrate_dispute. The phrasing implies a read operation for a single task's dispute, but it does not state exclusions or selection criteria.

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