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

No annotations are provided, so the description carries the burden. It usefully discloses the return payload fields, but says nothing about failure behavior for an unknown drug_id, whether results are cached/live, or any auth requirements. For a simple read-by-id lookup the risk is low, so partial coverage is acceptable.

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?

One tight sentence with no filler, and the key input (drug_id) is front-loaded. It is efficient, though the terseness leaves no room for routing or precondition context.

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 one-parameter lookup with no output schema and no annotations, enumerating the returned fields compensates reasonably well for the missing output schema. Only the absence of source/routing guidance keeps it from being fully complete.

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 single parameter's meaning ('id returned by search_drugs') is already documented there. The description repeats the identifier name but adds no syntax, format, or type nuance beyond it, so baseline 3 applies.

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?

States a specific verb and resource ('按 drug_id 取单条药品完整记录') and enumerates the returned content (indication codes, targets, approval date, company, links), which distinguishes it from the other entity-detail siblings at a glance. It does not explicitly name a sibling, but the resource noun carries the differentiation.

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?

No when-to-use or when-not-to-use guidance. The only hint that this is the detail counterpart to search_drugs appears in the schema ('search_drugs 返回的 id'), not in the description. An agent must infer the search-then-detail workflow.

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