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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — 'A pay-per-use leads tool' — signalling cost, but says nothing about auth, lead volume, or turnaround.

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 first sentence is truncated mid-thought with an ellipsis and then repeated almost verbatim in the next sentence, wasting roughly half the text. The core value proposition is still front-loaded and the length is short, so it is not penalized heavily.

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 one-input tool with no output schema, the description does sketch the return shape (companies, contacts, fit scores), which is helpful. But the nested input object is documented only by an external link, and the duplicated sentence dilutes rather than completes the picture.

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?

Only one nested input parameter and reported schema coverage is 100%, so the baseline is 3. The description's 'describe your ideal customer' loosely maps to that input but adds no structure or format detail beyond what the schema (and its pointer URL) already supplies.

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 states a specific input (an ICP description) and a concrete output (a ranked lead list with firmographics, contacts and fit scores), which is enough to distinguish it from generic scrapers. It does not, however, explicitly contrast itself with close siblings like qualified_leads or b2b_prospecting_pipeline.

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 when-to-use guidance, no prerequisites, and no alternative named among the many B2B siblings. 'Describe your ideal customer' implies the trigger, but the agent gets nothing on when this beats qualified_leads or b2b_crm_enricher.

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