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

With no annotations, the description assumes full disclosure burden and delivers richly: it reveals the adjudicator is the BlindOracle operator panel, the verdict is unilateral with no buyer contest channel, it is evidence-retained but not a disinterested referee, the live dispute_disclosure block is authoritative, there is no charge when the source cannot be fetched, and pricing is $5.00 USDC per call (x402). These are exactly the caveats an agent needs before invoking.

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?

Purpose is front-loaded and every sentence carries real information (verdict types, adjudicator identity, pricing, refund condition). It is dense rather than padded, though the long disclosure run-on could be trimmed slightly for readability.

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 mutation-style tool with no annotations and no output schema, the description covers outcome, ledger side-effect, adjudicator identity, and billing, which is substantial. The one gap is procedural: both sides 'submit evidence' yet the schema exposes only a single 'task' parameter, and neither description nor schema explains how evidence is supplied.

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?

Only one parameter ('task') exists and schema description coverage is 100%, so the baseline is 3. The description adds no syntax, format, or content guidance for the parameter, leaving the schema to carry it.

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 names a specific verb and resource ('Adjudication of a contested deliverable') and specifies the output artifact (signed verdict – upheld/overturned/withdrawn, ProofOfAdjudicatedOutcome 30129) written to a settlement ledger. It is a clear, distinctive purpose that no sibling tool plausibly duplicates, though it never explicitly routes against contenders like procurement.council or deliberation.multi-agent-debate.

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 scenario is implied (a contested deliverable where both sides submit evidence), which anchors when the tool applies, but there is no explicit when-to-use/when-not guidance and no named alternative for adjacent dispute or deliberation needs. Usage is inferable rather than stated.

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