vertical_search

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

Mentions returns structured payload, but lacks details on read-only nature, authentication, rate limits, or any side effects. With no annotations, more behavioral context would be helpful.

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 and examples, no redundancy, every part earns its place.

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?

Covers purpose and domain examples well, but given the complexity (5 params, nested objects, no output schema), lacks details on return format, pagination, or error handling.

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?

Adds meaning beyond schema by clarifying domain enum values (e.g., finance for tickers) and notes sub_domain_params must have required keys. Schema coverage is high, but description enhances usability.

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 it's a vertical-domain structured search tool with specific examples (finance, academic, security) and distinguishes from siblings like 'search' and 'vertical_batch'.

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?

Tells when to use (specific domains) and implies alternatives via sibling list, but doesn't explicitly state when not to use or mention alternatives within the description.

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