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

Annotations indicate readOnlyHint=true and openWorldHint=true, already signaling safe, non-deterministic behavior. The description adds context by naming the underlying API (nexgendata/lead-list-enricher) and specifying response-time considerations. No contradictions with annotations.

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 very concise: three short paragraphs with front-loaded purpose, usage guidance, and parameter details. Every sentence adds value, no redundancy.

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 single parameter, no output schema, and annotations present, the description covers purpose, usage, batch size, and parameter format. It does not detail the output structure, but the information provided is sufficient for an agent to use the tool correctly.

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 only parameter (domains) is described with format and example in the Args section, compensating for 0% schema description coverage. The description adds meaning beyond the JSON schema by clarifying it expects a list of company domains.

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 bulk-enriches company domains with contact information (emails, contact pages, social profiles, phone numbers). It distinguishes itself from sibling tools like 'sales-intelligence__enrich_company' and 'sales-intelligence__find_company_emails' by specifying bulk operation and the specific data enriched.

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 explicitly recommends using this tool after 'find_b2b_leads' and suggests a batch size of up to ~50 domains for performance. While it does not mention when not to use or list alternatives, the provided pipeline guidance is clear and useful.

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