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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: it separates source measurement time from Web3Juice retrieval time, and warns that links and labels are source-provided and unverified — a meaningful trust caveat not present in the structured data.

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 payload enumeration is front-loaded in the first sentence and the unverified-data caveat is placed last where it acts as a qualifier. Dense but every clause maps to an actual returned field; the single-sentence enumeration is long but not 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?

An output schema exists, so return values need not be documented, yet the description helpfully orients the agent to what the response contains. Combined with annotations covering the safety profile, nothing an agent needs to call this correctly is missing, apart from explicit sibling routing.

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 0%, so the description must carry the single parameter, and it does identify it as a pool id. However it adds no format or constraint detail (non-empty, max length 512) beyond what the schema's type already implies, leaving a modest but real gap.

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 and resource — retrieve full detail for one pool id — and enumerates the payload (APY split, TVL, timestamps, addresses, withdrawal evidence) so the agent knows exactly what it gets. It doesn't explicitly name a sibling to contrast with, but 'one pool id' distinguishes it from search_pools/get_pool_history by implication.

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: the description frames this as single-pool lookup, which suggests search_pools for discovery and get_pool_history for time series, but it never states when to prefer it or names any alternative. No prerequisites or exclusions are given.

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