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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: the result is paginated and the full set is large, which warns the agent to expect paging and heavy result volume. It stops short of return format or rate-limit details.

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?

Very compact and front-loaded, with the scale caveat placed before the endpoint note. The trailing 'DailyMed v2: GET /ndcs' is endpoint trivia that adds little for an agent, so it is not perfectly waste-free.

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 burden of describing the return, and it only implies a list of NDC codes without stating element shape or whether label metadata accompanies each code. Pagination behavior is hinted at and parameters are covered, so it is adequate but not 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 description coverage is 100%, so both parameters (page, pagesize) are already fully documented with defaults and maxima. The description's mention of 'paginated' merely echoes the schema rather than adding format or usage nuance, so the baseline 3 applies.

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+resource ('List National Drug Codes') and adds scope ('across all labels in DailyMed'), which distinguishes it from the per-label sibling dailymed_label_ndcs. An agent can tell what it returns without opening the 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?

Usage is implied by 'across all labels', suggesting a global enumeration rather than a per-label lookup, but no when-to-use/when-not guidance or explicit alternative (e.g. dailymed_label_ndcs) is named. The agent must infer the distinction from sibling names.

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