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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses the graph subset, the invisibility of non-indexed wallets, the interpretation of LOW, and the return components (collusionRisk, reciprocal cluster, coverage block). No side effects are claimed and nothing contradicts the annotations.

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 dense but every clause earns its place: scope parenthetical, detection definition, output summary, LOW caveat, and pairing suggestion. The purpose is front-loaded and there is no filler.

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 tool with no output schema and no annotations, the description explains purpose, scope, limitations, and output categories well. However, it leaves the `coverage` block undefined and never binds the input address to the analysis, so an agent may still be uncertain about how to invoke it and interpret all returned fields.

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?

The only parameter, `address`, has no schema description and schema coverage is 0%. The description never explains what the address represents, such as the wallet being screened for collusion, or how A/B maps to the input. This is a real gap because the description needed to compensate for the empty schema and did not.

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 states a specific verb ('detects') and resource ('MainStreet's indexed USDC transfer graph'), defines exactly what it looks for (reciprocal flow in a small counterparty set), and names the output risk levels. The tool's unique role is clear even among many mainstreet_* siblings.

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 gives strong usage context: it explicitly scopes the data to transfers whose recipient is an already-indexed payTo and warns that LOW means 'no reciprocity seen inside that perimeter', not a global negative. It also advises pairing with mainstreet_repeat_rate. It does not explicitly state when-not-to-use it, but the scoping and warning effectively guide usage.

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