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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuine value beyond them by stating 'Keyless' (no auth required) and enumerating exactly what the read returns (sponsor, ingredients, indications, PI/CMI links).

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?

Front-loaded with the resource and key, then the return contents, then an example. The inline example largely duplicates the schema's examples block, which is the only mildly wasted text; otherwise every clause earns its place.

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?

There is no output schema, so the description carries the full burden of describing the return value, and it does so comprehensively (sponsor, ingredients with strength, dosage form, route, indications, status, dates, PI/CMI links). Nothing essential for correct invocation 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?

Single parameter with 100% schema description coverage, so the schema baseline is 3. The description goes slightly beyond it by tying 'LicenceId' to its source (artg_search), giving the agent the provenance and expected format of the id.

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 (full ARTG record for one entry) and the keying identifier (ARTG ID / LicenceId), which cleanly distinguishes it from the sibling list/search/recent tools. An agent can tell what it retrieves 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 routes the agent: the id comes 'from artg_search', which clarifies when this tool is the follow-up to a search rather than a standalone lookup. It lacks an explicit when-not statement against artg_list/artg_recent, but the detail-vs-list distinction is clear from context.

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