Icon Composer MCP

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

No annotations provided, so description carries full burden. It correctly identifies the output format (.icon bundle) and target platform (Xcode 26). However, it fails to disclose critical file-system behaviors: whether it overwrites existing bundles, creates intermediate directories, or handles naming conflicts. Missing idempotency or safety information for a filesystem-writing tool.

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 sentences with zero waste. First sentence establishes inputs and action; second sentence clarifies output destination and format. Perfectly front-loaded with no filler content.

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 the rich parameter set (13 parameters controlling visual effects like specular, blur, translucency), the description is minimal. It doesn't explain what the resulting icon looks like, what Liquid Glass effects are, or how the various rendering parameters interact. However, with complete schema coverage and no output schema to document, it meets baseline adequacy.

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 adequately documents all 13 parameters. The description mentions 'foreground image' and 'background color', which maps to required parameters, but adds no semantic value beyond the schema's existing descriptions (e.g., doesn't explain Liquid Glass, specular highlights, or how glyph_scale affects the composition).

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?

Specific verb 'Create' with clear resource 'Apple Icon Composer .icon bundle' and input specification 'from a foreground image and background color'. The mention of 'Xcode 26' and the specific output format distinguishes this from sibling tools like read_icon (inspection) or add_layer_to_icon (modification).

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 explicit when-to-use or when-not-to-use guidance is provided. However, the specificity of inputs (foreground_path, bg_color) versus siblings implies this is the entry point for new icon creation versus manipulation of existing icons. Lacks explicit guidance on prerequisites like file permissions or when to use export_preview instead.

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