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

Annotations already establish readOnlyHint=true and destructiveHint=false, so no contradiction exists. The description adds useful behavioral context beyond annotations: it applies to both protocol versions, it returns a full capability list when 'lookingFor' is used, and it records gaps when a capability does not exist.

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 moderately sized and front-loaded with the core purpose before enumerating topics. The topic list is somewhat redundant with the schema enum, but it serves as a quick reference for the agent and the edge-case guidance about 'lookingFor' 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?

There is no output schema, but the description explains what the tool returns for the 'lookingFor' path and implies guidance content for the topic path. Given the tool's role as a meta-guide among many specialized siblings, the description covers the selection and invocation needs well, though it could state the return format for normal topic queries more explicitly.

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%, so the baseline is 3, but the description adds meaningful usage context for both parameters: it explains when to send 'lookingFor' versus when to omit it, and stresses that topic should be read before building an action. The topic list duplicates the enum but reinforces the intended workflow.

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 clearly states this is the protocol and usage guidance tool for building Aave flows, covering both v3 and v4. It differentiates itself from the many get_/prepare_ siblings by explicitly positioning itself as the fallback when no tool seems to fit and offering the 'lookingFor' capability to discover tools by intent.

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 explicit when-to-use guidance: read the relevant topic before constructing an action, and come here when no other tool seems to fit. It also gives a clear boundary by directing users to external docs for deep protocol documentation, which functions as a when-not-to-use signal.

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