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

Annotations already cover safety (readOnly, idempotent, non-destructive) and world scope, so the description is free to add the substance it does add: the openFDA US-label source, the specific flagged substances (gelatine, alcohol, pig-derived enzymes, heparin), and the output shape where the necessity ruling leads. That is genuine context beyond the structured fields, though it does not cover limits such as label unavailability or non-US products.

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 opening fragment 'Is this medicine halal?.' duplicates the title verbatim and wastes a sentence slot, and the second sentence is a dense semicolon splice mixing output-field naming with product guidance. The useful information (source, flagged substances, output ordering) is present but not cleanly front-loaded.

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 usefully names the leading fields (ingredient_headline, verdict) and explains the ordering rationale, and annotations carry the safety profile. It is close to complete for a single-parameter read tool, with the only gap being behavior when a label is missing or the medicine is not in openFDA.

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?

There is a single parameter with 100% schema description coverage ('Brand or generic name'), so the schema does the heavy lifting and the baseline is 3. The description adds nothing about accepted name formats (brand vs generic resolution), so it neither compensates nor detracts.

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?

The description states a specific verb and resource (reads a medicine's label and flags haram-relevant ingredients) and names the data source (US label / openFDA), which distinguishes it from the generic check_ingredients sibling. It stops short of explicitly contrasting itself with ask_is_it_halal or check_ingredients, so sibling differentiation is only implicit via the openFDA-medicine scope.

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?

Usage is implied rather than stated: an agent can infer this is for checking a named medicine, and the closing clause about the ruling on necessity signals that prescribed medicines should not be discouraged. There is no explicit when-to-use, when-not-to-use, or naming of the alternative sibling tools, so the agent must infer routing.

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