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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds value beyond those: it states exactly what is returned (title, publication date, announcement URL) and what is explicitly absent (approved-drug list), which is useful behavioral context for an agent.

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 compact, front-loaded with the core scope, and each sentence adds value: what the feed contains, example query forms, return fields, and the critical negative boundary. Minor redundancy in 'from the regulator' does not hurt usability.

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 simple two-optional-parameter read-only tool with strong annotations, the description is complete: it explains the domain, return values, section coverage, and the key exclusion. No output schema exists, so stating the return shape in the description fills that gap well.

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%, so the schema already documents limit and section, including the merge-and-sort behavior when section is omitted. The description's examples map query topics to the section concept, but it adds no parameter syntax or 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 names the exact resource (NMPA official announcements), enumerates content types (policy changes, guidance, import rules, clinical-trial guidelines, reform opinions), and explicitly contrasts itself with the drug-approval register. This makes it easy to distinguish from sibling tools like nmpa_drug_approval or nmpa_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?

It gives clear when-to-use signals via example queries like 'latest NMPA regulatory updates' and states a firm when-not: this is NOT the drug-approval register. It does not name the alternative tool by name, but the negative boundary is explicit and unambiguous.

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