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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds that the tool returns a full capability list and 'records the gap' when a capability is missing, which is useful non-obvious behavior. The 'records the gap' phrasing hints at a side effect not reflected in the annotations, but it reads as telemetry rather than data mutation, so no contradiction is flagged.

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?

Front-loaded with the core instruction and the fallback behavior before the topic enumeration. The 19-topic list duplicates the schema enum verbatim and is the one wasteful element in an otherwise tight definition.

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?

Both parameters are optional and fully described in the schema, and the description explains what the tool returns (guidance content or a capability list) despite there being no output schema. Only minor ambiguity remains about the shape and length of the returned guide 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 description coverage is 100% and the lookingFor parameter is already richly documented in the schema, including when to omit it. The description reinforces topic selection ('Read the relevant topic') and lists topic names, but the list merely duplicates the enum, so it adds little beyond structured fields.

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+resource: protocol and usage guidance for building Aave flows, with an enumerated topic set. It is clearly differentiated from every sibling, all of which are data-fetch or action-preparation tools, and it additionally declares itself the fallback when no sibling fits.

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?

Gives explicit timing: 'Read the relevant topic before constructing an action,' plus an explicit alternative path ('send lookingFor' when no tool seems to fit) with the condition that selects it. It also routes deep protocol questions out to docs.aave.com, so the agent knows when not to use this tool.

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