collections_export

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, permissions, output format, or whether this is a read-only or mutating operation. The phrase 'Export a collection' gives no insight into what actually happens.

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?

While the description is extremely short and has no wasted words, it is under-specified to the point of being unhelpful. It resembles a placeholder rather than a well-crafted concise description.

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?

With no output schema and minimal description, the tool's behavior, return value, and use case are entirely unexplained. For a simple tool it might be acceptable, but the description lacks even basic context about what 'export' entails.

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% coverage, with the id parameter described as 'Collection ID'. The description adds no additional meaning beyond the schema, but the schema already provides sufficient information for the single parameter.

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 states the action ('Export') and resource ('a collection'), which is clear enough to understand the basic purpose. However, it does not differentiate from sibling tools like collections_export_all, and the exact meaning of 'export' (file download, data format, etc.) is left vague.

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?

There is no guidance on when to use this tool versus alternatives. No context is provided about prerequisites, typical scenarios, or how it relates to collections_export_all or other collection tools.

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