export_documents_bulk

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

No annotations are provided, placing the disclosure burden on the description. The description implies a read operation ('export metadata') but does not explicitly state safety, side effects, or permissions required.

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?

Two concise sentences, front-loaded with the main action, no unnecessary words or repetition.

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?

No output schema is provided, and the description does not describe the output structure, return type (file, string, etc.), or any pagination/limitations, leaving the agent uncertain about what to expect.

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 has 100% description coverage, so the tool description adds minimal new parameter meaning. It mentions available formats (matching the schema enum) but does not clarify what 'metadata' includes.

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 exports metadata for multiple documents in three formats (JSON, CSV, Markdown), distinguishing it from sibling export tools that handle entities, relationships, or other 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 gives use cases ('reports, backups, sharing document lists') but does not explicitly differentiate this tool from alternatives or provide when-not-to-use guidance.

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