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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It implies a read/search operation and mentions evidence of public business contact, but it does not explain how ranking works, what output shape is returned, whether the tool scrapes live Google Maps data, or any rate, freshness, or compliance limitations.

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, front-loaded sentence with no filler. Every phrase contributes: the domain, the action, the ranking promise, and the contact-evidence criterion.

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 no-parameter tool this is serviceable but thin. It tells an agent what the tool returns at a high level, but without annotations or an output schema it does not convey result format, ranking basis, or scale. It is enough for selecting the tool, but not fully enough for confident invocation.

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 tool exposes zero parameters, and the baseline for a zero-parameter tool is 4. There is no schema parameter meaning to explain, and the description still adds useful domain context by specifying Google Maps as the source and B2B leads as the target.

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 names a specific action ('Find'), a distinct resource ('Google Maps B2B leads'), and an output qualifier ('ranked', 'public business contact evidence'). It is clearly differentiated from the sibling tools, which focus on trends, jobs, procurement, or content rather than place-based lead discovery.

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 guidance about when to use this tool versus any sibling, and no stated exclusions or prerequisites. An agent must infer appropriate usage from the name and short description alone.

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