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

Goes well beyond the annotations: it discloses the $0.01 price, the USDC-on-Solana x402 payment flow including the call-without-payment-then-retry-with-_meta pattern, the availability of a free preflight, that nulls are honest rather than fabricated, and that every response carries a benchmark label. readOnlyHint=false is not explicitly reconciled, but the paid call is a genuine side effect, so there is no contradiction.

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 payload shape, then pricing and payment mechanics, then the HTTP equivalent. Dense but every clause is informative; the payment-flow sentence is long but necessary for a paid tool.

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 carries the return-value burden and does so thoroughly — field list, computed gap, horizon set, null policy, and label sentence. The only material gap is input format guidance for 'ndc'.

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 0% and there is only one parameter, 'ndc', whose expected format (10- vs 11-digit, hyphenation, validation) is never stated in the description. 'Per-NDC' at least confirms the parameter's role, but nothing compensates for the missing format guidance.

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 resource (a per-NDC NADAC fact at the latest generation) and enumerates exactly what comes back: verbatim published fields, the computed corresponding-generic gap, and four horizon changes. It does not, however, distinguish itself from siblings like nadac_changes or nadac_dispersion, which an agent must infer from the single-NDC scope.

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?

Usage is only implied: 'per-NDC' signals a single-record lookup and the preflight endpoint is offered as a free validation step. There is no explicit when-to-use/when-not guidance and no routing to the sibling NADAC tools, so the agent has to infer the boundary itself.

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