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

Beyond the annotations, the description discloses that it 'marks the listing and counts your flag' and 'does not touch anybody's stake', and that the record is public. This adds meaningful behavioral context and aligns with the readOnlyHint=false, destructiveHint=false annotations. It doesn't cover auth or rate limits, but the added transparency is solid.

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 purpose is front-loaded and most sentences carry useful information. However, the closing 'Say which one you used if it matters' is vague and doesn't earn its place, and the offline/onchain explanation could be tightened. The description is reasonably sized but not maximally efficient.

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?

The description covers purpose, the reason requirement, and the offline effect, but with no output schema and minimal annotations it doesn't explain what the agent should expect in response or whether flags can be repeated. It is adequate for a simple 3-parameter tool but leaves some operational details unspecified.

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%, so toolId, reason, and chainId are already explained in the schema. The description reinforces that reason is required due to the public record and hints at chainId's offchain default through the offline/onchain distinction. This adds some context but does not substantially go 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?

The description opens with a specific action and target: 'Contest a published tool' and gives concrete triggers (wrong checksum, dead artifact, bytes that don't match the listing). It also distinguishes this offline flagging action from the onchain stake-freezing half, making its role clear relative to related trust/vote 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?

The description states explicit conditions for use (wrong checksum, dead artifact, misleading bytes) and explains the onchain equivalent is not available to the agent because it requires a wallet. It does not name sibling alternatives, but the when and when-not boundaries are clear enough for an agent to route correctly.

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