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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. Beyond that the description adds substantive context: that records identify the registrant/filing party rather than necessarily the physical manufacturer, and that limit is capped at 100, which prevents a common misread of the results.

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 usage condition is front-loaded and each sentence carries information: the search target, the input form, the limit cap, the registrant caveat and the scope disclaimers. It is efficient, though the final negative-scope sentence is somewhat expendable and could be folded into the usage guidance.

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 read-only, multi-parameter listing tool with no output schema, the description covers when to use it, what the input accepts, result size limits and an important interpretation caveat about registrant vs. manufacturer. The main remaining gap is disambiguation from the sibling get_registration_devices and any explanation of the offset/snapshot paging parameters.

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 only 25%, so the description must carry more of the load; it does explain company (accepting a Chinese company name or recorded English registrant name, with the example 江苏视准医疗器械有限公司) and limit (maximum 100). It leaves offset and the snapshot pagination parameter unexplained in the prose, and snapshot is only documented in the schema itself.

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 gives a specific verb (list/search) and resource (medical devices a manufacturer, registrant or company has listed in the China NMPA UDI database), and the title reinforces the company/registrant scope. It is clearly separable from siblings such as get_device_by_udi and search_china_medical_device because it is scoped to a company's portfolio rather than a single UDI or a category search.

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 states an explicit when-to-use ('Use before general web search when the user asks what medical devices a manufacturer... has listed') and adds when-not context by ruling out credit, market-share and safety interpretations. It does not, however, contrast itself with the closely related get_registration_devices sibling, which an agent would need to disambiguate at call time.

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