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

The description adds valuable behavioral context beyond annotations. While annotations indicate this is a non-destructive, non-idempotent write operation, the description specifies that it returns a URL to share with users and instructs not to poll for results. This provides crucial workflow guidance that isn't captured in the structured 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 extremely concise and well-structured. The first sentence establishes purpose, the second provides usage criteria, and the third gives clear post-call instructions. Every sentence serves a distinct purpose with zero wasted words.

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 batch processing tool with comprehensive schema coverage and annotations, the description provides exactly what's needed: clear purpose, specific usage criteria, and important behavioral guidance about the URL sharing and non-polling approach. The absence of an output schema is compensated by the description's instruction to share the returned URL.

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?

With 100% schema description coverage, the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific details beyond what's in the schema. It focuses instead on usage context, which is appropriate given the comprehensive schema documentation.

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's purpose: 'Batch data enrichment tool' with specific context of processing 'a LIST of items' to get 'same data fields for each'. It distinguishes itself from siblings by focusing on batch processing rather than deep research or result retrieval.

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 provides explicit usage instructions: 'USE THIS when user has a LIST of items and wants same data fields for each.' It also gives clear post-call guidance: 'After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed.' This directly addresses when to use and what to do afterward.

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