query

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the hybrid retrieval method and the return of Wiki snippets, but does not explicitly state whether the operation is read-only or what 'link expansion' entails in terms of side effects. More detail would improve transparency.

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?

The description is a single, concise sentence in Chinese that front-loads the action and result. Every word adds value, with no filler or repetition, making it both compact and informative.

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 simple tool with one parameter and an output schema, the description provides sufficient context: it explains what the tool does (hybrid retrieval + link expansion) and what it returns (Wiki snippets). It could be more complete by elaborating on 'link expansion' and potential prerequisites, but the current level is adequate for basic usage.

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% for the single 'question' parameter, so the baseline is 3. The tool description adds minimal extra meaning about the parameter beyond indicating it is the input for the retrieval process. It does not clarify format, length, or any constraints 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?

The description clearly states the tool performs hybrid retrieval and link expansion, returning relevant Wiki snippets. This is a specific action (retrieval) targeting a specific resource (Wiki snippets), and the inclusion of 'hybrid' and 'link expansion' differentiates it from sibling tools like read_wiki or write_wiki.

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 description implies the tool is for searching Wiki content based on a user's question, but it does not explicitly state when to use it instead of alternatives like read_wiki or ingest. No exclusions or alternative references are provided, leaving usage guidance to be inferred from the name and purpose.

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