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

No annotations are provided, so the description carries the burden. It discloses the 25-mint limit, the ranking behavior ('worst first'), the free single-token alternative, and that it returns x402 payment instructions. It doesn't mention failure modes or rate limits, but the disclosed behavior is substantial for a tool with no 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?

Three sentences with no filler. The core purpose is front-loaded, the limit is stated, the alternative is named, and the return type is disclosed. Every sentence earns its place.

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 bulk-analysis tool with 2 params and no output schema, the description covers purpose, scope, limit, ranking, payment instructions, and the cheaper alternative. It doesn't describe the exact response shape, but the description already says it returns x402 payment instructions, which is enough for an agent to invoke it correctly.

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. The description adds context for 'mints' (portfolio holdings, up to 25) and implies 'usd' is the test position size, but doesn't add much beyond the schema. Baseline 3 is appropriate.

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 specific verb ('exit analysis'), a resource ('portfolio'), and a clear scope ('up to 25 mints'). It also names the sibling tool 'exit_check' and distinguishes itself as the bulk/portfolio variant, so an agent can tell them apart without opening schemas.

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 explicitly says to use exit_check first for single-token analysis and that this tool exists for portfolios. It also gives a concrete question the tool answers ('of everything I hold, what am I trapped in?'), which is strong usage guidance.

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