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

Beyond the read-only, idempotent, open-world annotations, the description candidly discloses non-obvious behavior: the underlying SFDA site ignores search parameters, so filtering happens locally; each call scans only a bounded window of pages; and pagination is driven by next_page/done. This prevents false expectations about completeness of a single call.

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 information-dense yet economical: it front-loads the core search purpose, then explains source scale, local filtering rationale, pagination behavior, browse mode, and sibling routing in a single efficient paragraph. Every sentence contributes necessary operational knowledge.

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 tool with no output schema, the description does well to convey pagination fields (next_page, done), the nature of returned rows (details ref), and the bounded scan window. A minor gap is that it does not describe the exact row/response structure beyond the details reference, which would be helpful since no output schema exists.

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%, and the schema already documents query case-insensitivity, start_page zero-indexing/defaults, and pages_to_scan range/default. The description reinforces the pagination window concept but does not add meaningful parameter-level semantics beyond the schema.

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 uses a specific verb ('Search') and precisely defines the resource: Saudi Arabia registered human drugs with official SFDA prices in SAR. It distinguishes this tool from sibling sfda_drug_details by noting that each returned row carries a details ref for that separate tool. The scope and filtering behavior are unambiguous.

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 description gives explicit usage instructions: call repeatedly with the returned next_page until done:true to cover the whole list, omit query to browse pages, and use sfda_drug_details for per-drug detail. It clearly explains why the tool scans locally ('SFDA site currently ignores its own search parameters'), helping an agent decide when this tool is warranted.

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