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

Annotations only cover the safety profile (readOnly, idempotent, closed-world). The description adds real behavioral value by describing what comes back — named recommendations, formulation rationale, verbatim claim or a research-context note, price and purchase link — which is essential since there is no output schema.

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 trigger, followed by return content, then input guidance. Three sentences, each earning its place, though the middle sentence enumerating return fields is dense enough to border on catalogue-like.

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 zero-required-param lookup with no output schema, the description covers trigger, inputs and return shape adequately. It omits failure/empty-result behavior (e.g., when no authorized claim exists for a topic beyond the 'research-context note' hint), a minor gap.

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 individual field meaning is already documented. The description goes beyond it by explaining the relationship between the two optional params: supply a topic, or supply a plain-word concern that routes to one — a routing semantic the enum alone does not convey.

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?

Specific verb + resource ('recommend supplements') with the exact output enumerated: named product picks, formulation rationale, verbatim health claim, price and purchase link. It is clearly distinguishable from get_product_details and get_evidence, which concern raw data rather than curated picks.

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 an explicit trigger ('when the user wants specific supplement product picks for a topic') and states the input condition (a topic or a plain-word concern that routes to one). It does not name a when-not case or explicitly hand off to search_guidance/get_topic_guidance in the description, though the schema hints at it.

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