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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with an explicit 'no RPC, indexer, API, or other network request' guarantee, plus a pinned-snapshot disclosure that signals possible staleness. That is real added context beyond the annotations. The only shortfall is that it never says how current the snapshot is or how an agent should detect an out-of-date list.

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, front-loaded with the core behavior, then the negative guarantee, then the alternative data source and sequencing advice. No filler; every sentence carries decision-relevant 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?

An output schema exists, so return-shape explanation is unnecessary, and the remaining ambiguity for a zero-required-parameter read tool — is it live data, is it network-bound, what do I do with the result — is fully resolved in the text.

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 chain_id parameter is fully documented in the schema, so the schema already carries the semantics. The description adds only the framing that the listed markets are 'supported by the preparation tools', which is a marginal addition over the parameter's own text. Baseline 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?

States a concrete verb and resource — locally returns six major Aave V3 core deployments plus a bounded set of reserve/aToken/variable-debt-token addresses from a pinned address-book snapshot. It immediately distinguishes itself from discovery siblings (get_aerodrome_deployment, get_lido_deployment) by framing what is and is not covered, so an agent knows exactly what it gets without opening the 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?

Explicitly tells the agent when NOT to use this tool: live rates, caps, pause state, liquidity, collateral settings, eMode and account data must come from Aave's public GraphQL endpoint, which is named with a URL. It also gives a concrete sequencing instruction — intersect the API result with this fixed list before calling a preparation tool — routing the agent to the prepare_aave_v3_* siblings.

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