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

With no annotations, the description carries the full burden, and it does add real context: the dataset size (9.5k 行) and the tree/hierarchy nature including parent nodes. However it says nothing about return shape, the hard 20-row cap, or the 1000 offset ceiling that the schema enforces, so the behavioral picture is only partial.

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 compact sentence that front-loads the resource and the searchable fields with no filler. It is efficient, though the terseness borders on under-specification for a tool with pagination constraints.

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 search with 100% schema coverage and no output schema, the definition is minimally sufficient. It omits the practical limits (20-row hard cap, 1000 offset ceiling) and any signal distinguishing it from get_target_detail, leaving the agent to infer routing.

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 every parameter (limit, fields, offset, keyword) is already documented in the schema, including the hard cap and pagination ceiling. The description's mention of name/alias/parent node overlaps with the keyword parameter description and adds no syntax or format detail beyond the schema.

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 (检索/search) and resource (靶点树/target tree) and names the searchable fields (靶点名、别名、父节点), so the agent knows exactly what this returns rows from. It does not distinguish itself from siblings such as get_target_detail or search_drugs_by_target, which share the target domain.

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 explicit guidance on when to use this search versus get_target_detail for a single target, nor when to prefer search_drugs_by_target. Usage is only implied by the word 检索 and the listed searchable fields.

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