import_bot

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

With no annotations, description fully shoulders transparency. Discloses required file format, encoding method, authentication key, and plan-based rate limits. No omissions noted.

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 focused sentences. First sentence states core purpose, second sentence details requirements and constraints. No extraneous information.

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?

No output schema, so description should hint at return value or success/failure indication. It does not, leaving a gap for a creation tool. Otherwise, covers input and constraints well.

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 100%, but description adds value: clarifies base64 is 'the bot configuration package' and states the filename default. Goes beyond schema repetition.

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?

Clear verb 'import' and resource 'bot from a ZIP package'. Explicitly references sibling tools (export_bot/download_bot) for context on the expected ZIP structure, distinguishing it from other bot-related tools.

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?

States prerequisites (ZIP structure, base64 encoding, sk_* key, rate limits). Does not include when not to use or explicit alternatives, but the context is clear and covers usage constraints.

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