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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: California-only scope, keyless access, and the contents of the return ('launch WAC, estimated patient population, and breakthrough-therapy/priority-review FDA designations when disclosed'). It stops short of describing pagination or ordering behavior, hence not a 5.

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?

Purpose and scope are front-loaded and every clause carries information, but the single dense paragraph packs in regulatory context (CTRx program, WAC definition, Medicare Part D threshold) that could be tightened. Efficient but heavier than strictly necessary.

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?

With no output schema, the description compensates by enumerating the returned fields, and it covers geography, auth model, and the alternative tool. Complete enough to call correctly, though it omits result-count/ordering behavior that a no-output-schema tool could still clarify.

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 description coverage is 100%, so the schema already documents all four parameters with examples; baseline is 3. The description adds only the year range (2019-present) and echoes that drug/manufacturer accept fragments, which is marginal value over the schema's own examples and 'Omit to search every available year' note.

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 (discloses launch filings) and resource (California new prescription drug launch price reports), and explicitly distinguishes itself from the sibling ca_rx_wac_increases by naming the different trigger ('a NEW drug's starting price rather than an existing drug's price increase'). An agent can route between the two without opening either schema.

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?

Names the alternative (ca_rx_wac_increases) and the exact condition that selects this one vs. that one, plus the invocation modes ('search by drug name/fragment or manufacturer, optionally pinned to one report year'). The when-to-use vs. sibling is explicit rather than inferred.

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