search_tool

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

With no annotations, the description has full burden to disclose behavioral traits. It only states 'Full-text search across the wiki' without mentioning what is searched (page content, titles?), result format, ranking, rate limits, or auth requirements.

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. It is not verbose but also under-specifies some aspects; however, within its brevity it is well-structured.

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 there is an output schema (unseen), return values need not be described, but the description lacks context about search scope (e.g., titles vs full content), result behavior, and how it relates to sibling tools. Minimal for a search tool with many alternatives.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the parameter descriptions already present in the input 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 full-text search across the wiki, which is specific and not a tautology. However, it does not differentiate from similar list/search siblings like list_pages_tool or parse_wikitext_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?

No guidance is provided on when to use search_tool versus the 17 sibling tools, such as list_pages_tool or get_page_tool. There are no usage examples or alternative suggestions.

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