get_all_rxcuis

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

No annotations are provided, so the description carries the full burden. It discloses pagination support, which is useful behavioral context. However, it lacks details on rate limits, authentication needs, error handling, or the format/scope of returned data (e.g., whether it includes metadata or just codes).

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 a single, efficient sentence that front-loads the core purpose and includes essential behavioral context (pagination). There is no wasted verbiage or 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 no annotations and no output schema, the description is minimal but adequate for a read-only list tool. It covers the purpose and pagination but lacks details on response format, total count availability, or error conditions. It meets minimum viability but has clear gaps.

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 fully documents the two parameters (page and pageSize). The description adds no additional parameter semantics beyond implying pagination, which is already covered in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Get all available RxCUI codes'), the resource ('in the DailyMed database'), and includes a key behavioral trait ('with pagination support'). It distinguishes itself from sibling tools like 'search_rxcuis' by emphasizing retrieval of all codes rather than searching/filtering.

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 retrieving all RxCUI codes with pagination, which differentiates it from search tools. However, it does not explicitly state when to use this tool versus alternatives like 'search_rxcuis' or 'get_mappings_by_rxcui', nor does it mention any prerequisites or exclusions.

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