zoom_search

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

The description enumerates the types of outputs (answer, sources, warnings, metrics, evidence), which partially reveals behavior. However, no annotations exist, and the description does not disclose side effects, authorization needs, rate limits, or whether the tool is destructive. For a search-like tool, this is acceptable but incomplete.

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 a single sentence, achieving brevity. It front-loads the action and lists outputs. However, it could be more informative without increasing length, e.g., by noting the search technology or providing a hint about required parameters.

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 the tool complexity (9 parameters, 1 required, 0% schema coverage), the description is far from complete. An output schema exists, which helps for return types, but the parameter semantics gap and lack of usage guidance leave the description insufficient for an agent to effectively invoke the tool.

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 0% schema description coverage and 9 parameters, the description offers no explanation of any parameter. It does not mention the required 'question' parameter or optional ones like 'seed', 'output_mode', or numer results. This severely hampers correct invocation.

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 action ('Run Zoom Search') and the outputs (answer, sources, warnings, metrics, evidence). It is specific about the return value composition, which helps the agent understand the purpose. However, without sibling tools, differentiation is not tested, and 'Zoom Search' is not elaborated, so it is not a 5.

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 no guidance on when to use this tool, prerequisites, or alternatives. There is no mention of context or exclusionary criteria, leaving the agent with no usage heuristics beyond the name.

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