Search Leads V2

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It reveals nothing about side effects, read-only status, rate limits, authentication, output format, or what happens when a search URL is supplied. The phrase 'Provide search url' is an instruction, not a behavioral disclosure.

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 short, but it is under-specified rather than concise. It contains only one terse sentence and lacks structure, context, or any ordering of important information that would help an agent use the tool correctly.

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?

For a search tool with no output schema and no parameters in the schema, the description is not complete enough. It fails to explain the URL format, expected input mechanism, return value, or relationship to the many sibling search tools, so an agent cannot confidently invoke it.

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?

The schema has zero parameters, so the baseline is higher, but the description introduces an input concept ('search url') that is entirely absent from the input schema. An agent cannot determine how to pass the search URL or what format it should take, which creates confusion rather than adding useful parameter meaning.

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 is a directive ('Provide search url instead of filters') rather than a statement of what the tool does. It does not say whether the tool searches leads, returns results, or performs some other action; the tool's purpose is only inferable from the name 'search_leads_v2.'

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?

There is no explicit guidance about when to use this tool versus sibling tools. The phrase 'instead of filters' hints at a contrast with filter-based search tools like search_leads, but it does not specify conditions, exclusions, or alternatives clearly.

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