download_bot

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

With no annotations, the description provides good transparency: it discloses the output format (base64-encoded ZIP), instructs how to process the result (save and decode), and notes authentication (JWT). It could mention potential issues like token expiration, but covers key behaviors.

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?

Three sentences: first states purpose and contents, second explains return format, third gives usage instructions. No unnecessary words, information is front-loaded.

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 download tool with no output schema, the description covers input, process, and output handling. It does not cover error scenarios (e.g., expired token) but is sufficient for typical usage given the sibling tools and context.

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?

Both parameters are described in the input schema (100% coverage). The description reinforces that 'token' comes from export_bot and 'filename' is for metadata, but adds no new meaning beyond the schema descriptions themselves.

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 downloads a bot configuration ZIP package, specifies contents (bot.yaml, .env, commands/), and mentions prerequisite token from export_bot. It distinguishes from siblings by explicitly referencing export_bot as a prerequisite, clarifying its role in a two-step process.

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 specifies when to use this tool (after obtaining a token from export_bot) and notes authentication method (JWT, no API key). It does not explicitly state when not to use it or list alternatives, but the prerequisite guidance is clear.

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