Icon Composer MCP

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

With no annotations provided, description carries full burden and discloses rendering pipeline (ictool default, flat composite fallback) and external dependency (Icon Composer). Could improve by noting output format (PNG) or side effects like file overwrite behavior.

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 efficient sentences with zero waste. First sentence establishes core purpose and rendering engine; second lists key features. Information is front-loaded and every clause 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?

Appropriately complete for a 10-parameter preview tool. Schema handles parameter specifics; description focuses on rendering architecture and key capabilities. Lacks mention of PNG output (documented in schema) but sufficient given complexity and rich 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 has 100% description coverage (baseline 3). Description adds semantic value by explaining 'Liquid Glass' vs 'flat' rendering modes (contextualizing the 'flat' parameter) and highlighting canvas/zoom features, guiding effective parameter combination.

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?

Description uses specific verb 'Render' with resource '.icon bundle' and qualifies with 'preview' to distinguish from sibling 'export_marketing'. Mentions specific technology 'Apple's ictool/Liquid Glass' to differentiate from 'render_liquid_glass' and other tools.

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 implicit guidance by describing fallback behavior (flat composite when Icon Composer unavailable) and mentions 'flat' override capability. However, lacks explicit when-to-use guidance versus siblings like 'export_marketing' or 'read_icon'.

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