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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds the underlying endpoint (GET /drugclasses) and the shape of returned records, but says nothing about response volume, ordering, or whether the list is exhaustive — useful context beyond annotations is thin.

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?

A single compact sentence with the field enumeration up front, followed by the endpoint reference. Nothing is wasted, though the endpoint string is marginally redundant for an agent that never sees the HTTP layer.

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 naming the returned fields, and pagination is fully covered by the schema. For a simple read-only listing tool with annotations covering safety, this is close to complete; only usage routing is missing.

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 100%, so page and pagesize are already fully documented in the schema with defaults and bounds. The description adds no parameter detail at all, which is the correct baseline when the schema does the work.

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 pharmacologic drug classes linked to labels') and enumerates the returned fields (code, coding system, type, name), so the agent knows exactly what it gets back. It does not distinguish itself from siblings like list_drug_names or list_rxcuis, but the resource is distinct enough that confusion is unlikely.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. The phrase 'linked to labels' hints at context but never states when an agent should call this instead of search_labels or list_drug_names.

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