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

Annotations already indicate read-only, idempotent, open-world behavior. The description adds value by clarifying that manufacturer count is a CMS aggregate (not a list of companies) and specifying the 2020-2024 time range, going beyond what annotations provide.

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?

The description is two sentences: first sentence states purpose, second provides a crucial caveat about manufacturer count. Every word earns its place; no redundancy.

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?

Given the tool has an output schema (so return values need not be explained), the description covers purpose, key parameter, data source, time range, and a critical caveat. This is complete for a profiling tool with good annotations.

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 50%; the 'limit' parameter is documented, but 'generic_name' lacks description. The description compensates by stating the tool uses an 'exact generic name' and focuses on brand rows, adding meaning beyond the schema.

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 clearly states the tool profiles brand rows sharing an exact generic name, with manufacturer count and spending/use trends. It uses specific verbs and resources, distinguishing it from sibling tools like medicare_part_d_drug_spending.

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 implies usage for analyzing generic competition but does not explicitly state when to prefer this tool over alternatives such as medicare_part_d_drug_spending or medicare_part_d_prescriber_exposure. It provides context but lacks exclusion guidance.

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