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 and does a solid job: it declares this is a write tool, states authorization requirements, and discloses the all-or-nothing validation behavior ('if any errors, nothing is created'). It stops short of explaining whether existing resources are overwritten or merged, but covers the most critical behavioral traits.

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 compact and front-loaded: action, access requirement, format, and validation behavior each get one clear sentence. The Args section adds useful structure without bloat, and every sentence earns its place.

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 operation, the description covers authorization, format, atomic validation, and the payload's major sections, and an output schema exists for return-value details. The main gap is the lack of detail about what happens to existing resources on import, but the guide reference fills much of this.

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 input schema is nearly empty (an object with additionalProperties: true), so the description must compensate. It does name the payload format (JSON v2), enumerates the expected sections (version, connections, uploads, pipelines, transformations), and points to AI_IMPORT_GUIDE.md for details. This is meaningful guidance, though the description could be more self-contained about exact payload requirements.

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 opens with a specific verb and resource set: 'Bulk-import connections, uploads, pipelines, and transformations in one call.' This clearly differentiates the tool from singular siblings like create_connection and create_pipeline. An agent immediately understands the scope and one-call nature.

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 states the key precondition: write access must be granted via --allow-write or OAuth consent, and read-only sessions refuse the call. It also implies the use case by contrasting with single-create tools, though it does not explicitly name alternatives or say 'use create_* for single imports.'

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