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

Annotations already show readOnlyHint=true, so description is not contradicted. It adds valuable behavioral context: auto-narrows to hinted vertical, returns structured results (results_by_vertical, total_count, bookable_total). No extra info on auth or rate limits, but adequate for a read-only tool.

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?

Every sentence is purposeful. The core purpose is stated first, then usage guidelines, then return structure. No wasted words. Concise yet informative.

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?

With output schema existence and rich annotations, the description covers all needed context: what it does, when to use, auto-narrowing behavior, and key output fields. For a complex tool with 6 parameters, this is complete.

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%, but description adds practical meaning: 'empty string is fine (= browse)' for query, 'Optional time hint' for when with examples. This goes beyond the schema's basic 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?

The description clearly states the tool searches all Agentorist verticals at once, with a specific verb ('search') and resource ('every vertical'). It distinguishes from siblings like 'search' by explaining auto-narrowing behavior for single-vertical queries.

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?

It explicitly tells when to use (queries spanning verticals or vague) and when not to (specific single-vertical queries it auto-narrows, hinting to use sibling 'search'). Provides concrete examples ('what's on tonight', 'anything to do in Boston?').

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