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

With no annotations, the description carries the behavioral burden. 'List' implies a read-only operation, and the topic enumeration adds useful context, but it does not describe the return format, ordering, or whether each guide contains structured data or free text. For a simple listing tool this is adequate but not rich.

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?

One sentence immediately states the action and resource, then uses a compact parenthetical and colon list to enumerate content. No filler or repetition; every part adds value.

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?

This is a simple, parameterless listing tool with no output schema, so the description covers the essential purpose and scope. It might have mentioned how results are presented (e.g., titles/IDs), but the low complexity means the current description is sufficient for correct invocation.

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?

There are zero parameters, so the description is not required to add parameter meaning. The description's list of guide topics effectively communicates what the result set contains, which is the only relevant semantic content for this tool.

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 uses a specific verb ('List') and clearly identifies the resource ('comparison guides'), then enumerates the exact topics included. This distinguishes it from siblings like get_guide (which presumably returns one guide) and search_supplements (which searches supplements).

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?

The description makes the use case evident: call this tool to see available comparison guides on specific supplement forms. It does not explicitly state when not to use it versus get_guide or search_supplements, but the enumeration of guide topics provides clear context for selection.

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