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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds little beyond 'paste domains, get fit scores' — no mention of processing time, cost, data retention, or what happens to unmatched domains. For a scoring pipeline over arbitrary scraped input, the behavioral gaps (asynchronous? batch limits?) are left entirely unexplained.

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-phrase and then repeated verbatim in the second, burning space without adding information. What remains is short and front-loaded, but the duplication is clear 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?

No output schema, no annotated properties on the nested input object, and no description of what a 'fit score' or 'signal tag' response looks like. For a tool whose entire value is a scoring output, the definition is not complete enough for an agent to invoke it confidently.

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?

There is one parameter and the schema nominally covers it at 100%, but that 'coverage' is a generic nested object pointing at an external URL with no defined sub-properties. The description only hints at the input shape ('paste domains', 'any lead scraper output'), which is somewhat useful but far from a usable contract. Baseline 3 given nominal full coverage.

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?

States a concrete verb and resource: turns scraper output into ICP-scored, signal-tagged accounts, and mentions the input modality (paste domains). It is clear what the tool produces, but it never distinguishes itself from close siblings like ai_company_enrichment, b2b_intent_radar, or google_maps_lead_enricher. The duplicated/truncated opening sentence also slightly muddies the read.

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 only usage signal is the loose claim 'Works with any lead scraper output.' There is no statement of when to pick this over the many sibling enrichment/scoring tools, no prerequisites, and no exclusion criteria. An agent gets no routing help.

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