enrich_batch

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

Covers concurrency and cascading, but no annotations exist. Missing details on rate limits, failure handling, or auth requirements beyond the api_key parameter.

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?

Two concise sentences front-load the key behavior (concurrency, cascading). No extraneous information.

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?

Adequate given output schema exists, but lacks details on batch size limits, error aggregation, or when cascading stops (e.g., on first success/failure).

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 coverage is 100%, so parameters are already described. Description adds no new semantic value beyond the schema.

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?

Description clearly states 'Enrich multiple leads concurrently' with cascading behavior, distinguishing it from single-lead sibling tools like enrich_lead and enrich_company.

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?

Implies batch usage but lacks explicit when-to-use or alternatives guidance. Doesn't contrast with enrich_lead for single leads or check_usage for quota checks.

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