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

Annotations already cover readOnly and closed-world, but the description adds meaningful context: deterministic evaluation, no wallet action, no signing, no chain read unless a separately requested preflight asks for it. It does not disclose what the result envelope contains or how a 'BLOCK'/'REQUIRE_APPROVAL' outcome is surfaced.

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 clauses, front-loaded with the cost and the verb, followed by the behavioral disclaimer. 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?

The mutation-free nature is well covered and the safety profile is reinforced, but with a nested 0%-coverage schema, no output schema, and no disclosure of result shape, the definition leaves the agent guessing about what to populate and what to expect back.

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 0% across three top-level params and a deeply nested action/policy structure. The description names the policy axes conceptually (network/token/spender/value) but supplies no field-level meaning, no enum semantics (ALLOW/REQUIRE_APPROVAL/BLOCK), and no required-vs-optional guidance, so it only partially compensates for the empty schema descriptions.

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 (inspect), resource (ERC-20 allowance/revocation request), and the policy dimensions checked (network/token/spender/value). It is clearly distinguished from siblings observe_allowance (reads chain), preflight_allowance (simulates a transaction), and get_receipt.

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?

Clarifies the cost (FREE) and the no-side-effect/no-signing/no-chain-read profile, which routes agents to preflight or observe when those are needed. It does not explicitly name the sibling alternatives or state when-not-to-use beyond the preflight caveat.

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