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

With no annotations, the description carries the full burden and does meaningful work: it declares the paywall, says it returns x402 payment instructions for a specific endpoint, and specifies the ranking behavior ('ranked worst first') and the 25-mint batch cap. It doesn't state what happens to positions that fail mid-analysis or how partial results are returned, leaving some behavioral surface uncovered.

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-loads the critical constraint (PAYWALLED) and the purpose, then layers scope, behavioral outcome, payment mechanics, and the sibling alternative. Four short sentences, no filler, each carrying distinct information.

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 annotations and no output schema, the description is nearly self-sufficient: purpose, batch limit, ranking, paywall mechanics, and alternative are all covered. It stops short of explaining the x402 payment flow end-to-end or error/partial-failure behavior, a modest gap for a mutation-ish analysis tool.

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 both parameters are already documented (mints up to 25, optional usd position size). The description restates the 25-mint limit but adds no syntax, format, or defaulting detail for usd beyond what the schema provides, which is the expected baseline.

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+resource (portfolio exit analysis over up to 25 mints) and the exact question it answers ('of everything I hold, what am I trapped in?'). It explicitly distinguishes itself from the sibling exit_check by scope (one token vs portfolio), so an agent can route without opening either schema.

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?

Names the alternative ('For one token use exit_check') and states the selecting condition (this one is for portfolios), covering both directions of the routing decision. The PAYWALLED prefix also signals the prerequisite before the agent commits to a call.

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