scrape_leads

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

The description mentions 'background job' but does not disclose what that entails (e.g., async behavior, job ID returned, how to check status). With no annotations, the description carries full burden for behavioral traits like rate limits, authorization needs, or potential impact. This is insufficient, especially for a mutation 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?

The description is one concise sentence that immediately communicates the core action and outcome. Every word serves a purpose, and the most critical information ('background job') is front-loaded.

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 8 parameters, no output schema, and no annotations, the description is severely lacking. It fails to explain what the background job returns (e.g., job ID), how to monitor progress, or how the optional parameters affect the search. The agent has insufficient context to use this tool correctly without external documentation.

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 100%, so the schema already documents each parameter. The description does not add meaning beyond that (e.g., how parameters interact, examples, or constraints). Baseline 3 is appropriate given high coverage, but no extra value is provided.

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's purpose: scraping leads from Google Places based on a query and location. It uses a specific verb ('scrape') and resource ('leads from Google Places'), and it distinguishes from sibling tools like get_leads and export_leads by indicating it initiates a background job.

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 versus alternatives such as get_leads (retrieving existing leads) or export_leads (exporting). It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage based solely on the tool's name and purpose.

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