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

No annotations are provided, so the description carries the full burden. It does disclose the matching mechanism (encoded 阶段|适应症名|适应症id string) and an extra return field (indication_matched), which is useful behavioral context. However, it omits that this is a read-only search, how pagination limits interact, and any scope constraints beyond what the schema already documents.

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 compact sentences with the core purpose front-loaded, followed by the matching and return detail. No filler, though the parenthetical encoding string is dense and would benefit from a touch more structure.

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?

With no output schema, the description should carry return-value explanation; it partially does by describing the indication_matched field but does not describe the overall result shape (drug rows) or field-selection behavior. Adequate for a filtered-search tool but with visible gaps.

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%, so the schema already documents all five parameters, including the default/hard cap on limit and the offset+limit<=1000 constraint. The description adds only marginal meaning by clarifying what the indication keyword is matched against, so the baseline 3 is appropriate.

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+resource ('按适应症找药品' = find drugs by indication) and names the exact field being matched (rs_medical.indication), which makes its role distinguishable from search_drugs and search_drugs_by_target. It stops short of explicitly naming those sibling alternatives, so it is clear but not sibling-differentiating.

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?

There is no guidance on when to use this tool versus search_drugs, search_drugs_by_target, or search_indications. No prerequisites, exclusions, or context conditions are stated; the agent must infer the selection logic from the tool name alone.

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