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

With no annotations, the description carries the full behavioral burden. It usefully discloses that data is a daily snapshot of DefiLlama's feed and enumerates the returned fields including derived flags, but says nothing about not-found/error behavior, auth, or rate limits. 'Look up' implies a safe read, but that is left to inference.

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?

Two tight sentences: the lookup action and return payload are front-loaded, and the snapshot-provenance note is a single qualifying clause. Nothing is redundant or padded.

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-parameter read tool with no output schema, the description covers the action, the identifier, and the returned fields, including the freshness caveat that matters for interpreting APY/TVL. Only the not-found/error path is unaddressed, a minor gap for a simple getter.

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 pool_id property already documents the UUID format with a concrete example. The description restates 'DefiLlama pool UUID' without adding format, validation, or fallback detail beyond the schema, so it matches the baseline for fully documented parameters.

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 gives a specific verb ('look up'), a scoped resource ('a single pool'), the identifier type (DefiLlama pool UUID), and even the return contents (APY breakdown, TVL, anomaly/below-floor flags). It implicitly contrasts with the plural find_pools, but never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage is only implied: an agent can infer this is for retrieving one known pool when it already has a UUID, as opposed to searching. There is no explicit when-to-use / when-not-to-use, no mention of prerequisites, and no pointer to alternatives like find_pools or get_pool_score.

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