generate_expo_icons

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

With no annotations provided, the description carries the burden of explaining side effects. It clearly states that files are generated into assets/images/, but it does not explicitly warn about overwriting existing files or mention prerequisites like the need for a transparent PNG. The schema documents the overwrite parameter, but the description itself is thin on behavioral details.

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 a single sentence that directly conveys the purpose and enumerates the outputs. Every word earns its place; it is concise and 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?

The description covers the full scope of generated outputs and the target directory. Given the rich schema (including nested proportions and defaults), the description is sufficient for an agent to select and invoke the tool. It could mention the required source image or the fact that it writes files, but those are present in the schema.

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 100%, so the schema already documents all parameters and their defaults. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Generates') and resource ('all 10 Expo assets'), explicitly listing each output (icon, android adaptive, splash, favicon, react-logo, partial). This clearly distinguishes it from sibling tools like transform_image or convert_svg, which handle generic transformations or conversions.

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 states the tool's output directory and the full set of generated assets, providing clear context for when to use it. However, it does not explicitly mention when not to use it or name alternatives, such as using transform_image for one-off resizing.

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