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

With no annotations provided, the description carries the full transparency burden. It discloses the data source (public CMS data) and pricing ($0.1/call) but lacks details on rate limits, authentication requirements, data freshness, or behaviors like empty result handling. Some disclosure is present but incomplete.

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 concise: two sentences plus a parameter list. It front-loads the purpose with an example, then lists parameters and closes with data source and pricing. Every sentence adds value with 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?

The tool is moderately complex with 9 parameters. The description explains the concept and key parameters but lacks information about the output format (e.g., list of prescribers with shift values) and pagination details. Without an output schema, the description could more fully set expectations.

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 input schema has 78% description coverage (high), so baseline is 3. The description adds value by explaining the share calculation (molecule claims ÷ class claims) and providing concrete examples for key parameters like drug_class and molecule. This goes beyond the schema's basic descriptions.

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 'Find' and identifies the resource 'prescribers with within-class molecule mix shift year-over-year'. It provides an example (GLP-1/Tirzepatide) and lists parameters, making the tool's purpose clear and distinct from sibling tools like prescribers_partDClassYoyDelta_search which focus on class-level shifts.

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 gives a concrete example but does not explicitly state when to use this tool versus alternatives. It implies usage for molecule-level share shifts but leaves the agent to infer when not to use it. No exclusion criteria or alternative tool mentions are provided.

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