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

Annotations already mark this as read-only, idempotent, open-world, and non-destructive. The description adds valuable behavioral detail beyond those hints: the tri-state semantics of revert vs. no-data vs. false, the exact cost of $0.001 USDC per call, supported chains, and byte-identical equivalence to a REST endpoint. This gives the agent a clear model of what the call will and will not tell it.

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 compact and front-loaded with the most important semantic distinction, followed by cost, supported chains, and an exact equivalent endpoint. Every sentence earns its place, and there is no filler or repetition of schema content.

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 simple two-parameter, read-only tool with a full input schema and output schema, the description is complete. It covers purpose, semantic nuance, cost, chain support, and an exact endpoint equivalent. An agent has everything needed to select and invoke the tool correctly, and the output schema handles return-value expectations.

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 the schema already documents both parameters and their formats. The description repeats the chain list and provides an example address in the endpoint, but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate because the description does not need to compensate for missing parameter documentation.

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 title and description clearly identify the operation: checking whether a contract is paused via paused(). The description goes further by distinguishing three possible outcomes (no pause switch, not paused, reverted), which makes the tool's purpose precise. It does not explicitly differentiate from sibling tools, but no sibling appears to offer the same paused-check semantics.

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 implies when to use the tool: when you need to know whether a token/contract is paused and care about distinguishing 'no pause switch' from 'not paused'. It does not explicitly state when to prefer this over alternatives such as chain_call or chain_contract_check, nor does it mention any exclusions. The cost and chain list provide practical context but not usage routing.

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