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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds one behavioral detail (that output carries human-facing labels plus values to send back), but says nothing about snapshot/retention behavior tied to as_of, which the schema merely documents factually.

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?

Two compact sentences, front-loaded with what the tool returns and followed by the single precondition. No wasted text.

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?

For a simple two-parameter read with full schema coverage and no output schema, the description conveys the content of the response (forms, strengths, labels, values) adequately. Minor gap: no mention of snapshot/retention limits around as_of, but the tool's complexity is low enough that this is not crippling.

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 both id and as_of are already documented in the schema. The description's 'use the id from a search hit' reinforces the id semantics but adds no format or range detail for as_of beyond what the schema provides; baseline 3 applies.

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 clear verb+resource: it returns the forms (tablet, liquid, patch) and strengths a medication comes in. The added note about 'labels for people and values to send back' clarifies the shape of the payload, distinguishing it from sibling lookups like get_packages or lookup_ndc, though it never names an alternative explicitly.

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?

'Use the id from a search hit' gives a concrete precondition, routing the agent to search_medications first. However, there is no statement of when to prefer this over get_drug, get_packages, or other sibling tools, so usage is implied rather than delimited.

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