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

No annotations are provided, so the description must carry behavioral disclosure. It usefully reveals the underlying match field and the returned value format (e.g. 'ADRB(批准上市);GR(批准上市)'), but says nothing about permissions, result ranking, or what happens when a target matches nothing. Pagination caps are handled by the schema, not the description.

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?

A single front-loaded sentence with the core purpose first and the technical detail confined to a parenthetical. No wasted clauses, though the parenthetical format sample is slightly dense.

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 usefully sketches the return shape (target strings annotated with approval status), and the schema covers all four parameters including pagination limits. It is nearly complete for a simple filtered search; only the absence of alternative-routing guidance and empty-result behavior keeps it short of full.

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 limit/offset/fields/target are all documented in the schema itself; the baseline of 3 applies. The description only adds that matching occurs against rs_medical.target with status-annotated values, which is modest value beyond the schema's own 'target name' example.

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 target') plus the exact field matched (rs_medical.target) and the drug-status scope (in-development/marketed). This distinguishes it from search_drugs and search_drugs_by_indication without opening their schemas, though it never names those siblings explicitly.

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 purpose sentence implies the usage context (locate drugs when you have a target), but there is no explicit when-to-use, when-not-to-use, or routing to the sibling search_drugs_by_indication for indication-based lookups. Usage is only inferable.

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