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 usefully discloses the shape of what is returned (upstream ancestor chain, downstream children, associated drug count), but says nothing about read-only nature, error behavior for a missing/invalid id, or response size.

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 dense sentence, front-loaded with the identifier and the action, followed by the returned fields. Nothing is wasted and nothing is buried.

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 correctly compensates by enumerating the returned elements (ancestors, children, drug_count), which is the key information for an agent deciding whether to call it. It is adequate for a simple one-parameter read tool, with only error/edge behavior left unstated.

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?

Only one parameter and schema description coverage is 100% — the schema already documents target_id as 'the id returned by search_targets'. The description restates that the id selects the target but adds no format, type, or edge-case detail beyond the schema, so the 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 in Chinese (按 target_id 取靶点 = fetch a target by target_id) and even previews the payload (ancestor chain, child targets, drug count). It is clearly distinguishable from the search_* siblings by being the id-based detail fetch, though it does not explicitly name an alternative tool.

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?

Usage is only implied: the phrase 'by target_id' plus the schema note that the id comes from search_targets signals this is the follow-up call to a search, but the description itself never says when to use this versus search_targets or what happens for an unknown id.

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