toggle_web_search

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

No annotations exist, so the description must fully disclose behavior. It mentions the mutation via '[mutation]' and states the effect (AI can search internet), but omits critical details like persistence, scope (per-conversation or global), or permissions required. This leaves ambiguity about side effects.

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?

Two sentences and a tag—every sentence adds value. The action is front-loaded, and the description is efficient with zero wasted words.

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 toggle with two parameters and no output schema, the description covers the main behavior and use case. However, it fails to mention the 'prompt' parameter (why it's needed and that it is preserved), which is a notable gap in completeness.

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?

Input schema has 100% coverage, so parameters are documented structurally. The description adds no additional meaning to the 'prompt' parameter and does not explain its role beyond what the schema provides. With full schema coverage, baseline score of 3 is appropriate.

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 toggles web search for the AI, with a specific verb ('activate/deactivate') and resource ('web search'). It distinguishes from sibling toggle tools (e.g., toggle_analytics) by naming the exact feature.

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 usage context—when the AI needs up-to-date internet info (trends, prices, news). However, it does not explicitly state when to avoid using it or provide alternatives, missing guidance on when not to enable or disable.

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