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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as rate limits, authentication requirements, or what happens with empty results. The phrase 'hottest cold-outreach leads' adds value but insufficiently covers behavioral aspects.

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 concise sentence that front-loads the key function. It is efficient but lacks structural elements like bullet points or sections. It earns its place without waste.

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 has 4 parameters (2 required), no schema descriptions, and no annotations, the description is moderately complete. It states the core purpose but omits details about output format or limits, despite an output schema existing. Adequate but not thorough.

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 description coverage is 0%, yet the description does not elaborate on any parameters. While parameter names like 'niche' and 'city' are somewhat self-explanatory, no additional meaning or format guidance is given, leaving the agent to rely solely on the schema.

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 finds businesses in a niche with no website, which is distinct from siblings like 'find_no_booking' and 'audit_website'. The verb 'find' and resource 'businesses without website' are specific, and the value proposition for cold outreach is highlighted.

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 implies use for cold-outreach leads without websites but provides no explicit guidance on when to use vs. alternatives like 'search_businesses' or 'audit_website'. The context is clear but lacks exclusions or comparative advice.

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