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

Annotations already mark this read-only, open-world, idempotent, and non-destructive, and the description adds useful behavioral context: no wallet/API key required, $0.02 per-call cost, free daily tier, optional prepaid header, and Base-network scope. It does not conflict with the annotations.

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 front-loads the core question and outcome, then gives reasoning, use case, required input, pricing, and access details. It is slightly colorful with the rug metaphor, but every sentence adds either purpose or operational context.

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 paid, network-specific tool with an output schema and strong annotations, this description is remarkably complete: it states inputs, outputs, use case, pricing, free-tier behavior, auth requirements, and network. Nothing essential is left for an agent to guess.

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 this is already well-covered. The description still adds meaning by clarifying the address is a Base token contract and that the tool consumes a Base token plus a trade size in USD, which helps an agent map inputs to the expected network and purpose.

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 states a clear verb+resource: it estimates buy and sell price impact and reports whether a given USD size can be unwound without collapsing the pool, plus the largest safe exit. It is specific and distinctive, but it does not explicitly differentiate itself from closely related siblings such as sellability.

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 gives a clear use context: 'Built for trading agents sizing positions' and frames the tool as an exit-feasibility check before holding a token. It does not explicitly name alternatives or when-not-to-use conditions, so it misses the top tier.

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