export

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

The description only states the action without detailing behavioral aspects like whether the export is returned as a file or string, or if any side effects occur. The annotations already indicate read-only and non-destructive behavior, so the description adds no new insights.

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 concise single sentence with no redundant words. It front-loads the action and clearly communicates the core function without unnecessary detail.

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?

Despite the tool's complexity—including nested exportTarget objects for find and aggregate operations and four required parameters—the description offers minimal high-level context. It does not mention the need for database/collection or how the export is performed, making it insufficient for an agent to fully understand the tool's scope.

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 description contains no parameter-specific information, but the input schema provides comprehensive descriptions for all parameters (100% coverage). The brief mention of 'specified EJSON format' does not add value beyond the schema's detailed explanation of jsonExportFormat.

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 function: exporting query or aggregation results in EJSON format. It uses a specific verb and resource, and the mention of EJSON format distinguishes it from sibling tools like 'find' or 'aggregate' that return data without exporting.

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, such as using 'find' or 'aggregate' for direct querying. No exclusions, prerequisites, or alternative tool references are given.

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