Icon Composer MCP

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

No annotations provided, so description carries full burden. Discloses key behavioral traits: output format constraints (no alpha, opaque), default dimensions (1024x1024), and flat rendering (no Liquid Glass). Missing only file overwrite behavior and error conditions.

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 tightly constructed sentences with zero redundancy. Front-loaded with purpose, second sentence delivers technical specifications. Every word earns its place.

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 exists, but description compensates by detailing output characteristics (format, opacity, dimensions). Given the 3 parameters are fully schema-documented and the domain complexity is moderate, the description provides sufficient context for correct invocation.

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%, establishing baseline 3. Description reinforces the size default ('1024x1024 (default)') and implies output_path produces a PNG, but doesn't add syntax details beyond schema descriptions.

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?

Excellent specificity: 'Export a flat marketing PNG for App Store Connect' provides exact verb, resource, and destination platform. Explicitly distinguishes from siblings by stating 'No Liquid Glass effects' (contrasting with render_liquid_glass) and 'flat' (contrasting with export_preview).

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?

Provides clear context (App Store Connect upload requirements) and constraints (no alpha channel, opaque PNG). Implicitly signals when not to use it ('No Liquid Glass effects'), though it doesn't explicitly name render_liquid_glass as the alternative for that use case.

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