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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real value: the US-label/openFDA provenance, the specific substances flagged, and the deliberate design of leading with a necessity ruling so prescribed medicine is not stopped. Missing rate-limit or label-availability caveats.

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 user-facing question, then the mechanism and the output shape in two tight sentences. Every clause carries information, though the 'so nobody stops a prescribed medicine' rationale is slightly discursive rather than operational.

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?

No output schema exists, so the description must carry the return-shape burden, and it names the returned fields (ingredient_headline, verdict) plus the source and its US-scope limitation. For a single-parameter read tool, an agent has everything needed to call and interpret it.

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?

Only one parameter (name) with 100% schema description coverage ('Brand or generic name'), so the schema already carries the semantics. The description does not add format guidance beyond implying a medicine name; baseline 3 applies when structured data does the heavy lifting.

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 concrete verb and resource — reads a medicine's active and inactive ingredients from its US label via openFDA and flags specific haram substances (gelatine, alcohol, pig-derived enzymes, heparin). The medicine-specific, US-label, openFDA framing clearly separates it from generic siblings like check_ingredients and check_product_by_barcode.

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?

The domain (medicine) and data source (openFDA label) imply when to reach for this tool, but no alternative is named. An agent must infer whether check_ingredients, check_product_by_barcode, or ask_is_it_halal is the better fit for a non-medicine or non-US-label query.

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