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

Goes well beyond the read-only/idempotent annotations: discloses the $0.02 cost, that payment is USDC on Base, that the response returns POST instructions rather than a paid result, that baselines expire after seven days, and that reads are block-pinned. These are exactly the operational traits an agent needs before invoking a paid tool.

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?

Front-loaded with the core purpose, then constraints, then payment/logistics; every clause carries information. It is dense and the telegraphic final fragments ('USDC on Base. Costs $0.02.') read abruptly, but nothing is wasted.

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?

With no output schema, the description carries the return burden and does so reasonably — 'field-level evidence and unknowns' plus the note that a POST instruction set is returned instead of results. It is complete for invocation; only the exact shape of the evidence/unknowns payload is left implicit.

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 schema already documents address, pool (with its token0()/token1() constraint) and baseline. The description restates the seven-day baseline signing and same-pool pool semantics but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 resource and method: a Base token change report that compares signed seven-day baselines against block-pinned owner, pause, proxy and supply reads. It also names what it deliberately does not do (no honeypot simulation, sell-tax estimate, or safety guarantee), which separates it from check_token_security, though it never names a sibling directly.

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?

Implied workflow is clear — pass a baseline from a previous paid response for the same address/pool to get a change report — and the explicit exclusions ('No honeypot simulation, sell-tax estimate...') tell the agent when not to use it. It stops short of naming the sibling to use instead for those excluded questions, so it is not a full 5.

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