bulk_import

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

With no annotations, the description properly discloses the write requirement, validation-first behavior, and JSON v2 format. However, it does not mention error handling details beyond 'nothing is created'.

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 concise with two paragraphs and an Args section. It could be more structured (e.g., bullet list), but every sentence adds value 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?

Given the tool's complexity and the existence of an output schema, the description covers purpose, prerequisites, validation, and payload format. It lacks detail on return values or error responses, but the output schema presumably handles that.

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 0% for the payload parameter. The description adds critical meaning: it explains the payload structure (version, connections, uploads, pipelines, transformations sections) and references a guide, greatly compensating for the schema gap.

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 verb 'bulk-import' and lists the specific resources (connections, uploads, pipelines, transformations) in a single call. This distinguishes it from siblings like create_connection and trigger_pipeline which handle individual resources.

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 specifies a prerequisite (requires --allow-write) and validates before creating. It implicitly suggests use for bulk operations, but does not explicitly state when to prefer this over individual create tools.

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