get_all_pharmacologic_class_setids

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

No annotations are provided, so the description carries full burden. It mentions the tool retrieves SET IDs with associated drug mappings, implying a read-only operation, but lacks details on permissions, rate limits, pagination, or output format. This is inadequate for a tool with zero annotation coverage.

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 directly states the tool's function without fluff. It is front-loaded with the core action and resource, making it easy to parse quickly.

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 incomplete. It doesn't explain what a SET ID is, the format of the returned data (e.g., list, JSON structure), or any behavioral aspects like error handling. For a tool in a complex domain with many siblings, more context is needed.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing on the tool's purpose. Baseline is 4 for zero parameters, as it avoids unnecessary repetition.

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 verb 'Get' and the resource 'all pharmacologic class SET IDs', specifying they must have associated drug mappings. It distinguishes from siblings like 'get_all_drug_classes' or 'get_pharmacologic_class_details' by focusing on SET IDs with mappings, but doesn't explicitly contrast with 'get_pharmacologic_class_mappings_for_setid' which retrieves mappings for a specific SET ID.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't explain if this should be used for bulk retrieval of SET IDs before detailed lookups with 'get_pharmacologic_class_mappings_for_setid' or 'get_pharmacologic_class_details', or how it differs from 'search_drugs_by_pharmacologic_class' which might involve SET IDs.

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