create_export

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 uses the verb 'initiate' which suggests a side-effect (creating an export) but does not explain whether the operation is asynchronous, what it returns, or any side effects beyond creating a record. Permissions and rate limits are also undisclosed.

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 sentence and front-loads the key action and resource, which is efficient. However, it is terse to the point of under-specification for a tool with 10 parameters, and the sentence could easily have been expanded with useful context without becoming verbose.

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?

The tool has 10 parameters, no output schema, and no annotations, so the description must be comprehensive but is not. It fails to explain what the tool returns (e.g., an export ID), how to track the export, or the meaning of the many include flags for archived items. This is inadequate for an agent to use the tool correctly.

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 0%, and the description does not explain any of the 10 parameters, including required ones like 'include_passwords' and 'include_websites'. The only parameter hinted at is 'format' via the mention of 'PDF or CSV', but that information is already present in the schema enum. The description adds no meaningful parameter context.

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 ('Initiate'), the resource ('export'), and the scope ('of a company'), and specifies the two output formats ('PDF or CSV'). It distinguishes from the sibling 'create_s3_export' by mentioning the formats, though it does not explicitly contrast with that alternative.

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 no guidance on when to use this tool versus alternatives such as 'create_s3_export' or 'get_export'. There is no mention of prerequisites, context, or conditions that would make this tool the right choice.

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