wiki_search

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'full-text search' without explaining search scope (title/content), pagination behavior, ordering, or case sensitivity. The output schema exists but the description gives no hint about return format.

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, front-loaded sentence that efficiently conveys the tool's purpose. However, it sacrifices completeness for brevity, leaving gaps in usage and parameter details. It earns its place for purpose clarity but not for other necessary information.

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?

Given the tool's complexity (3 parameters, many siblings, an output schema), the description is incomplete. It lacks parameter explanations, usage context, and behavioral details that would help an agent correctly invoke it.

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 0% and the description adds no meaning to the three parameters (query, page, page_size). It fails to clarify the query format, default behaviors, or constraints beyond what the schema already provides.

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 '全文搜索 Wiki 文档' clearly states the tool's function: full-text search over Wiki documents. It uses a specific verb-resource combination and distinguishes this tool from sibling tools like wiki_get_document (retrieve single) or wiki_list_children (list hierarchy).

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 provides no guidance on when to use this tool versus alternatives. For example, it does not differentiate between using this search tool and wiki_list_children for finding documents, nor does it mention prerequisites or scenarios where search is preferred.

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