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

With no annotations, the description carries the full burden and does well: it discloses rate limits (3/hr shared with website), pricing ($0.015/call over x402), and the facts-only, non-advisory stance. It omits response format and error behavior, but the core behavioral contract is clear.

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-loads what is assessed before moving to pricing and access terms. One sentence covers scope and another covers commercial/limit details with no padding.

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 single-param lookup at 100% schema coverage with no output schema, the description supplies purpose, scope, usage stance, and access constraints. What is missing (response shape, error cases) is secondary for this profile.

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% and the single parameter already documents the DefiLlama pool UUID format and source URL. The description adds no additional meaning about the pool parameter, so the baseline of 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?

The description names the resource ('pool'), enumerates the specific checks performed (peg, yield sustainability, emission dependence, exit depth), and the tool is distinguishable from siblings like safety or stable.

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?

It gives clear context that this is for pool safety analysis and states 'Facts and flags only, never advice', which sets usage boundaries. It does not explicitly name when to prefer a sibling such as safety or exit_cost.

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