swarmtrade_dispute_trade

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

Discloses two key behaviors: freezes escrow and escalates to arbitration. No annotations provided, so description carries full burden. Lacks details on reversibility or permissions, but adds value beyond schema.

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?

Two concise sentences with no unnecessary information. Every word contributes meaning.

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?

Covers purpose and key behaviors adequately for a 2-param tool. No output schema, so explanation of return values is missing, but overall sufficient for agent decision.

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 coverage is 100% and parameters are already well-described. Description does not add extra meaning beyond the schema.

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?

Description clearly states the action 'Dispute an escrowed trade' and specifies the resource (escrowed trade). It distinguishes from siblings by mentioning freezing escrow and arbitration, contrasting with resolve_dispute.

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?

Implied usage for disputing escrowed trades but no explicit when-to-use or when-not-to-use guidance, nor comparison with swarmtrade_resolve_dispute.

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