download_character_zip

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

With no annotations, the description carries full burden. It discloses a side effect: 'Saves it to the pixellab-forge-output directory and returns the file path.' However, it does not mention potential overwrites, idempotency, or permission requirements. The download action implies a read operation, but no destructive hint is given.

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 two sentences, front-loaded with the key action, and contains no extraneous information. Every word contributes to understanding.

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 covers the main function, side effect, and return value. It could mention error cases (e.g., if character_id does not exist) but is otherwise complete.

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% (one parameter). The description does not add meaning beyond the schema's 'Character ID' description. No format, origin, or context is provided for the ID, which is adequate but not enhanced.

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 states 'Download a character as a ZIP file with all sprites and metadata' with a specific verb ('download') and resource ('character as a ZIP'). It distinguishes from sibling tools like list_characters (listing) and get_character (retrieving data, not a zip). The action and result are clear.

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?

No guidance is provided on when to use this tool versus alternatives like get_character or delete_character. It does not specify prerequisites (e.g., the character must already exist) or exclude scenarios where this tool would be inappropriate.

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