wiki_search

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

No annotations are present, so the description should disclose side effects, permissions, or rate limits. It only explains the search functionality and parameters but does not mention whether it is read-only, modifies data, or requires any special access. For a search tool, it is likely safe, but this is not stated, leaving transparency lacking.

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 concise, uses a clear docstring format with an 'Args' section, and each sentence serves a purpose. It is well-structured and easy to parse, with no fluff or redundant 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?

The tool has a simple search function, and the description covers its purpose and parameters. An output schema is present, so return values need not be described. However, it does not mention potential error conditions or pagination behavior beyond the limit parameter, which would be nice but is not strictly necessary for this simple tool.

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?

The description comprehensively explains all three parameters: query as space-separated terms, limit for maximum results with a default, and subdir for scoping. This adds meaning beyond the bare schema definitions, which have no descriptions. The coverage is complete and helpful.

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's purpose: 'Search wiki pages by keyword.' It uses a specific verb and resource, distinguishing it from sibling tools like wiki_read_page or wiki_list_pages. The action is unambiguous and matches the tool name.

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 explains what the tool does but does not explicitly state when to use it over alternatives, such as against wiki_hits_analysis or wiki_cluster_pages. However, the tool's straightforward search function and the distinct names of siblings make the use case reasonably implicit. No explicit 'use when' or 'don't use when' guidance is provided.

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