download_card_image

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

No annotations are provided, so the description carries full burden. It mentions downloading and saving to disk with a success/error return, but does not disclose behavior such as what happens if the card has no image, if the output directory does not exist, or if the file already exists. Limited behavioral disclosure.

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?

Description is concise and front-loaded with the main action. The Args/Returns format is clear. However, the default values are redundant with the schema defaults.

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?

Given 3 parameters, no annotations, but has output schema (not shown). Description lacks details about file format, permissions, error handling, and what happens to existing files. For a download tool, more completeness is expected.

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 description coverage is 0%, so description must compensate. It lists arguments: card_id, output_dir (with default), filename (optional). This adds basic meaning beyond the schema, but does not explain card_id format, whether output_dir must exist, or file extension.

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 'Download a card/question image and save it to disk.' This provides a specific verb (download and save) and resource (card/question image). It distinguishes from siblings like 'get_card_image' which likely returns the image rather than saving to disk.

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 on when to use this tool vs alternatives like 'get_card_image' or 'download_all_dashboard_cards.' No prerequisites or context are provided.

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