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

With readOnlyHint and idempotentHint already provided, the description contributes context by stating it selects the 'single best-matching filing' and returns the same fields as nmpa_drug_approvals plus a 'filing headline summary'. This adds meaningful information beyond 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?

The description is three sentences, clear, and front-loaded. The Chinese translation sentence is somewhat redundant but harmless and does not hurt understanding.

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?

Together with the schema and annotations, the description is almost sufficient. It explains the return relationship to nmpa_drug_approvals and the extra headline. A minor gap is that neither parameter is required in the schema, yet the description doesn't state that one must be provided; agents might call with no arguments.

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?

Input schema coverage is 100% — both `id` and `name` are fully described. The description mentions using a drug name, code, or company for `name`, but this is redundant with the schema; no substantive semantic detail is added.

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 starts with a specific verb and resource: returns one NMPA drug-approval record by id or name. It also differentiates from sibling nmpa_drug_approvals by saying to browse there if you don't already have an id.

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 explicitly tells the agent to use nmpa_drug_approvals to browse first if you do not already have an id, clearly scoping when this tool is appropriate and naming the alternative.

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