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

Annotations already cover read-only and non-destructive behavior, so the description's burden is lower. It adds useful context: it applies to both versions, returns an overview of tool families/prompts/guides, and tells the agent to answer from the result. It does not detail return format, but for a zero-parameter read-only orientation tool this is not a significant gap.

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 concise sentences with no filler. The when-to-use and how-to-use guidance are both explicit, and the description is appropriately front-loaded for an agent scanning tool definitions.

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 no-parameter, read-only overview tool, the description covers scope of content, trigger condition, and how to use the returned information. The only minor ambiguity is 'both versions,' but this does not prevent an agent from invoking the tool correctly.

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?

The tool has zero parameters and the schema is fully documented/covered, so there are no parameter semantics for the description to add. The description appropriately focuses on usage context instead, and the baseline of 4 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?

The description states a specific verb ('Call this') and a clear resource: the Aave server/connector's capabilities, including tool families, ready-made prompts, and guide topics. It clearly distinguishes itself from the many data-retrieval sibling tools by positioning this as the orientation/overview tool.

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 an explicit trigger condition: call when an Aave conversation opens with no specific request. It also provides a direct behavioral instruction to answer from this tool's content rather than guessing from tool names, which is especially valuable given the large sibling list.

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