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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description still adds real substance: the five-section output shape, per-row citations and source locators, and the upstream sources (national registers, ClinicalTrials.gov, monographs). It says nothing about pagination behavior despite limit/offset parameters, which is the remaining gap.

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 what-and-sections statement is front-loaded in the first sentence, and the provenance/coverage routing is appended. The sourcing sentence is long but carries decision-relevant information; little is wasted, though it could be trimmed.

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 does the heavy lifting on return structure (five named sections, every row cited) and provenance, which is what an agent needs to interpret results. The omission of limit/offset semantics and any hint of result volume is the only material gap for a 4-parameter tool.

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 50%: condition_id and jurisdiction are already documented in the schema. The description does add value by implying jurisdiction filters only the approved-medicines section ('by country or region'), but limit and offset receive no explanation anywhere. Baseline 3 is appropriate for mid coverage.

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 and resource — 'All medications and treatments on record for a condition' — and then enumerates the five fixed sections returned. This is clearly distinguishable from siblings like get_substance_uses (substance-centric) and find_trials (trial-centric), so an agent can route 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?

Explicitly says the tool is a lookup of sourced records and 'never a recommendation', and routes the agent to get_coverage for the register/jurisdiction list. It does not, however, state when to prefer find_trials or get_substance_uses instead, so the sibling exclusions are only implicit.

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