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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is already given. The description adds real value by noting the challenger must post a bond (funds movement) and supply an evidence hash, but omits what happens to the bond on failure, whether the action is reversible, and any authorization requirements.

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?

Three short sentences that are front-loaded with the action and then the requirements. No filler, though it is terse to the point of omitting useful routing and consequence information.

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?

Five required params, no output schema, and a mutation with financial stake. The return value (transaction hash) is stated, which is helpful, but the description does not cover the dispute lifecycle or bond consequences, leaving gaps for a tool of this complexity.

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 100% with all five params documented (address, milestoneIndex, challengerBond, challengerEvidenceHash, reason). The description restates bond and evidence hash at a high level but adds no format or unit detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'File a dispute against a milestone on-chain.' This is clear enough to distinguish it from read-side siblings like get_escrow_dispute and other dispute tools such as dispute_verification or raise_ip_dispute, though it does not explicitly contrast with them.

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 when-to-use guidance, no prerequisites beyond the implied bond, and no routing to alternatives such as dispute_verification or raise_ip_dispute. The agent must infer context entirely from the name and required params.

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