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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds context by identifying the external source (www.sfda.gov.sa details_data pages) and clarifying that the result mirrors every field shown on the SFDA details page. It does not describe failure modes or freshness, but the safety profile is already covered by annotations.

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 sentences carry all essential information with no filler. The core purpose and source are front-loaded, and the parameter instruction is placed at the end where it is easy to act on.

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 low-complexity read tool with two well-documented parameters and rich annotations, the description covers what the tool does, where the data comes from, which sibling tools to use first, and how to supply the required parameters. Nothing essential is missing for correct invocation.

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 coverage is 100%, and the schema already explains that 'id' is the row id and 'nid' is the list node id. The description's 'Pass the nid and id from a row's details ref' reinforces but does not materially extend the schema's own parameter documentation.

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 clear purpose: fetch the full SFDA record for one entry, listing example fields like registration number, trade/scientific name, and price. It explicitly distinguishes this from list-returning siblings by saying it operates on 'one entry from a list returned by sfda_drug_search or sfda_drug_shortages'.

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?

It names the exact parent tools whose output should precede this call and tells the agent to 'Pass the nid and id from a row's details ref.' This is explicit when-to-use guidance that routes the agent away from unrelated sibling tools.

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