bulk_import

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: uses Google Places for venue matching, name matching for artists, automatic deduplication, and server-side handling to avoid timeouts. It does not clarify whether operations are idempotent or what happens on duplicate detection, which is a minor gap.

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 three concise sentences, each adding value: first defines purpose, second details matching, third covers timeouts and dry-run. It is front-loaded and well-structured with 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?

For a complex bulk import tool with nested parameters and no output schema, the description covers purpose, deduplication, matching, dry-run, and server-side handling. It lacks details on error handling, rate limits, or concurrency, but generally provides sufficient context for an agent to use it 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?

Schema coverage is 100% and the schema descriptions are already detailed. The description adds high-level context (e.g., 'structured data' and 'Google Places'), but does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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: 'Bulk import structured data (artists, venues, events) into BNDY with automatic deduplication.' It uses a specific verb ('import') and resource ('BNDY'), and distinguishes from sibling tools (e.g., create_artist, create_event) by focusing on bulk operations and deduplication.

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 implies when to use this tool (for bulk imports, server-side to avoid timeouts) and mentions a dry-run mode. However, it does not explicitly state when not to use it or provide direct alternatives, leaving some ambiguity for the agent.

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