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

With no annotations provided, the description carries the full transparency burden and succeeds: it outlines what data is returned, notes that the tool is free, and explicitly spells out two interpretational limitations (independence does not prove separate parties, and all-time records do not guarantee current activity). This goes well beyond a typical description and prevents misuse.

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 front-loaded with purpose and output categories, followed by cost, limitations, and accepted inputs. It is longer than typical, but every section earns its place, especially the caveats that are essential for correct interpretation. A slightly tighter layout would push it to 5.

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 single-address check with no annotations and no output schema, the description is remarkably complete: it covers the trigger, the data fields returned, the caveats, the cost, and the accepted input formats. An agent has everything needed to call and interpret the tool correctly.

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%, so the baseline is 3, but the description adds meaningful semantics by enumerating accepted address formats: EVM, Cardano (addr1…), and Solana. The schema only says 'the address you are about to pay or hire,' so the description enriches the parameter with concrete acceptance criteria.

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 the exact use case ('Before paying or hiring an agent') and specifies the resource ('what the chain records about that address'). It enumerates distinct output categories (independent payers, paybacks, concentration, ACP jobs, service responsiveness, last payment), making it easy to distinguish from siblings like counterparty_bulk or counterparty_history.

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 clearly states when to use the tool: before paying or hiring an agent. It does not explicitly name alternative tools for other scenarios, so it earns a 4 rather than a 5, but the context is strong enough that an agent can infer this is the single-address pre-payment check.

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