scout_search

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

Without annotations, the description reveals that results are ranked JSON and that 'deep' depth triggers agentic multi-step search with progress reporting. However, it does not disclose side effects, rate limits, authentication needs, or response structure.

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 consists of two short, impactful sentences. The first defines the core function, and the second provides a key configuration detail. No redundant or unnecessary 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 description covers the main function and a key parameter but lacks details on result structure, pagination, error handling, rate limits, or how it compares to similar sibling tools. For a tool with 4 parameters and no output schema, more context is needed for full autonomous agent use.

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 significant semantics to the 'depth' parameter by explaining the 'deep' option's behavior (agentic multi-step, progress reporting). This goes beyond the schema's 'Search depth' description.

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 'Search the live web and return ranked results as JSON,' specifying the verb, resource, and output format. It distinguishes from sibling tools like scout_scrape or scout_screenshot by focusing on general web search with ranked results.

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 provides a usage tip for the 'depth' parameter but does not explicitly guide when to use this tool over siblings like scout_answer or scout_extract. The implied usage is for general web search, but no exclusions or alternatives are mentioned.

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