create_account_export

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

Discloses authentication method ('Authenticated via API key'), concurrency limits ('Max 10 concurrent requests'), and mode handling ('Respects read-only and dry-run modes'). Annotations provide no behavioral info, so this adds significant value. Could mention what happens when limit is reached, but still strong.

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?

Well-structured with a clear first sentence, usage guidelines, behavioral notes, and structured Args/Returns sections. A bit long but all content earns its place; could trim slightly.

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?

Covers the complete workflow: start, poll, check existing. References sibling tools. Includes Returns section with JSON fields. With output schema existing, the return description is extra but helpful.

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?

With 0% schema coverage, the description fully explains both parameters: include_stages with examples and clarification that each named category is added, and account with cross-reference to MAILCHIMP_API_KEY_<NAME> and list_accounts. Excellent compensation.

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 purpose: 'Start an account export job covering the requested categories of account data.' It uses a specific verb-resource combination and distinguishes from siblings by referencing polling and checking existing exports.

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?

Explicitly tells when to use the tool ('Use to request a downloadable archive of account data'), when to poll, and recommends using list_account_exports before starting a new one, providing clear alternatives.

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