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

The annotations already establish this as a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context beyond that: filters are applied server-side, Arabic enum values are translated to English, and originals are preserved in *_ar fields. The Hijri-calendar note also clarifies data semantics.

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 description is a single dense sentence that front-loads the resource, lists the data fields, and then records two important behavioral caveats. Every element earns its place and no filler is present.

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?

Given the schema fully documents the parameters and annotations cover the safety profile, the description provides the remaining context: source, field scope, server-side filtering, localization behavior, and Hijri dates. Minor details such as result count or pagination behavior are already addressed in the schema's page parameter.

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 the schema already documents all five parameters. The tool description adds no parameter-level detail beyond what the schema contains, so the baseline score of 3 is appropriate.

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 clearly identifies the resource: drug companies and manufacturing sites registered with the SFDA, and enumerates the returned fields. It lacks an explicit imperative verb such as 'List' or 'Search', but the noun-phrase framing is unambiguous and sufficiently distinct from sibling tools like sfda_drug_search or sfda_drug_approvals.

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?

No guidance is given about when to prefer this tool over sibling SFDA tools, nor are exclusions or prerequisites stated. The mention of filters implies a query-style use, but there is no explicit when-to-use or when-not-to-use framing.

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