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

No annotations, so the description carries the full burden. It discloses the shape of what comes back (existence flag, paid period, signed statement, renewal history) and that it is a read lookup, which is useful. However it says nothing about authorization, rate limits, error behavior when no record exists, or freshness of the signed statement.

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?

Two sentences, front-loaded with the resource being fetched and followed by the usage note. Dense but every clause maps to a distinct returned field or the caller's intent; only the long first sentence risks overload.

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 read whose output schema exists, the description supplies enough context: what a caller gets and why they would call it. Nothing essential is missing, though auth/error semantics remain unaddressed.

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 single 'address' parameter has 0% schema description coverage, so the schema contributes nothing. The description compensates by stating "Send an EVM address," which constrains the expected format and chain domain beyond the bare string type.

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?

Names a specific resource (the standing clearance on file for a wallet) and enumerates what it conveys: cleared-buyer existence, paid period, signed sanctions statement, renewal count and next renewal. This is far more than a restatement of the name. It stops short of 5 because it never distinguishes itself from the similar-sounding sibling 'cleared_buyer'.

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?

"A seller reads this before taking a job instead of paying for a screen" gives a concrete use context and implicitly positions it against paid screening. There is no explicit when-not or named alternative tool, so it is clear context without exclusions.

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