web_search

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

No annotations provided, so description bears full burden. It explains the search function and available engines but omits details on side effects (e.g., read-only nature), required permissions, or rate limits. Adequate but minimally transparent.

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 with front-loaded purpose, no waste. Every sentence adds essential information (engines, shortcuts, reference to sibling tool). Highly efficient.

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 three parameters and no output schema, the description covers the tool's purpose, engine options, and custom shortcut concept. It directs to a sibling for details. Complete enough for typical use, though return format is not mentioned.

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?

With 100% schema coverage, the description enriches parameter meaning by listing built-in engine examples and explaining custom shortcuts. This adds value beyond the schema's basic property descriptions.

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?

Clearly states 'Search the web using a search engine or custom website shortcut', providing specific verb and resource. Distinguishes from sibling tools like 'search' (likely internal) and 'list_search_shortcuts' (for managing shortcuts).

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?

Directs users to 'Use list_search_shortcuts to see all available' custom shortcuts, offering clear context. However, it does not explicitly state when not to use this tool or provide alternatives for different scenarios.

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