batch_import_documents

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Import' which implies a write operation, but doesn't clarify permissions required, whether it overwrites existing documents, error handling for invalid data, or the response format. This leaves significant gaps for a mutation tool with potential side effects.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a tool with one parameter and good schema coverage, making it easy to parse while conveying the essential 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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after import (success/failure responses), doesn't mention constraints like size limits or rate limits, and provides minimal guidance on usage context. Given the complexity of bulk operations and lack of structured safety information, more behavioral context is needed.

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 description coverage is 100%, so the schema fully documents the single 'documents' parameter and its nested structure. The description adds minimal value by mentioning 'predefined JSON structure' which aligns with the schema, but doesn't provide additional context about format expectations or usage examples beyond what's in the schema descriptions.

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 action ('Import multiple documents in bulk') and the method ('using a predefined JSON structure'), which distinguishes it from single-document operations like create_document. However, it doesn't explicitly differentiate from other import-related tools like import_markdown, leaving some ambiguity about when to choose this specific bulk import method.

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 no guidance on when to use this tool versus alternatives like create_document for single documents or import_markdown for different formats. It mentions 'bulk' but doesn't specify thresholds or scenarios where batch processing is preferred, nor does it mention prerequisites or constraints for bulk operations.

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