Minion Web Search

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that it performs a 'live web search' and returns a 'ready-to-display Minion verdict,' but does not reveal additional behavioral details like rate limits or result fallback logic. With annotations covering the core traits, the description provides moderate added value.

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 only two sentences long. The first sentence states the core purpose, and the second provides usage guidance. No unnecessary words or repetition. Every sentence contributes meaning.

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 purpose, usage context, and hints at the output format. Given that there is an output schema (present but not shown), the description does not need to detail return values. It is sufficient for an agent to understand when and how to invoke the tool, though a bit more detail on the verdict structure could enhance 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% description coverage for all parameters, so the schema already documents each parameter. The description does not add extra semantic context beyond the schema. Per calibration, baseline is 3 when schema coverage is high, and no additional value is provided here.

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 it performs live web searches and returns a formatted verdict with ranked sources. It also distinguishes itself from sibling tools by directing users to use it instead of a separate host search tool, though siblings (minionify, minion_chat, minion_bun_hunt) are unrelated to search.

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 explicitly says to use this tool for online lookups, recommendations, and shopping requests instead of a separate host search tool. It provides clear context but does not specify when not to use it, though the positive use cases are well defined.

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