topai_ai_web_search

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety and world-model profile is covered. The description adds 'noise-free organic results' and 'stateless, read-only execution,' which reinforce but largely restate the annotations. No pagination, rate limit, latency, or freshness-window detail is added.

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?

Four sentences, front-loaded with the purpose and result shape, then routing rules. Slightly verbose with the 'stateless, read-only execution' clause that duplicates annotations, but no wasted sentences.

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?

Covers purpose, result contents, usage routing, and safety state for a simple 2-parameter read tool. No output schema, but the description names the return shape (titles, canonical URLs, snippets), which suffices. Lacks freshness/pagination hints but those are minor here.

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%, with both query and max_results fully documented including bounds and default. The description adds no syntax, format, or operator guidance beyond the schema, so baseline 3 applies.

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 (executes a real-time web search query) and resource (organic results with titles, URLs, snippets), and explicitly distinguishes itself from two named siblings (topai_web_to_markdown, topai_google_ai_overview). An agent can route correctly without opening other schemas.

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?

Provides explicit when-to-use (up-to-date external facts, news, URL discovery) and two explicit when-not-to-use clauses with named alternatives and the condition selecting each. This is textbook routing guidance.

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