export_bot

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

With no annotations provided, the description carries full burden. It discloses that the token/URL are temporary and time-limited. However, it does not state whether the operation is read-only or if it modifies the bot (though export generally doesn't), nor does it mention authorization needs.

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 sentences, front-loaded with the action verb 'Generate.' No redundant words; every sentence adds necessary information including the ZIP contents and the follow-up tool usage.

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?

For a simple tool with one parameter and no output schema, the description adequately explains the purpose, output (token and URL), and next step. It could be improved by specifying the output format or validity duration explicitly, but the reference to download_bot fills the gap.

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 coverage is 100% with a single parameter 'botid' described as 'The numeric bot ID.' The description adds value by explaining that this parameter identifies the bot to export and what the export contains, giving context beyond the bare schema.

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 generates a temporary JWT token and download URL for exporting a bot configuration as a ZIP file, specifying the exact contents (bot.yaml, .env, commands/). It distinguishes itself from sibling tool download_bot by describing the sequential workflow.

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 explicitly tells the agent to use download_bot with the returned token to fetch the actual ZIP, providing clear sequential guidance. It also notes the time-limited nature of the URL, setting proper expectations.

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