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

Annotations declare readOnlyHint=false while the description reads like a pure lookup ('resolve', 'lists'), and it never discloses what, if anything, the non-read-only behavior mutates — tail risk left unexplained. It does add useful behavior beyond annotations: clarification guidance on ambiguous matches, source attribution, and telemetry exclusion.

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 purpose and packed with dense, relevant rules; there is no filler. Slightly run-on with several distinct constraints concatenated, but every sentence carries a usable instruction.

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?

An output schema exists, so return-value shape needn't be re-explained, and the description still notes sources and clarification guidance. The main residual gap is the unexplained non-read-only annotation, but for a 3-optional-filter lookup this is largely complete.

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% with enums and descriptions, so baseline is 3; the description adds value by mapping colloquial product names to specific filter combinations (brand+audience, ingredient) that the schema alone doesn't convey. It also reinforces 'combined filters must all match,' though some schema text is repeated.

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 (resolve) and resource (ordinary public product names / medicine labels), and clarifies it returns matching calculator bottles plus separately marked reference-only formulations. Distinct from siblings like get_label_directions and list_calculator_bottles, which the name alone might confuse.

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?

Provides concrete mapping examples (Children's Motrin → brand motrin + audience children; Walmart → brand equate), states 'omit filters only when unspecified,' and warns that unlisted brands are unsupported rather than substituted. Strong when-to-use guidance, though it never names which sibling to use for adjacent tasks (directions, question guides).

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