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 discloses scope (all groups, all four effect types) but omits mutation safety details like whether this overwrites existing individual effect states or if the operation is reversible.

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?

Single dense sentence with zero waste. Front-loaded with action verb, parenthetical enumeration is efficient, and 'at once' placement clearly signals bulk operation. 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?

Appropriate for complexity: explains domain-specific terms (Liquid Glass), scope (every group), and resource (.icon bundle). Lacks only error condition or prerequisite disclosure, which is reasonable given no output schema and simple param structure.

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% coverage (baseline 3). Description adds value by enumerating the specific effects (specular, shadow, blur, translucency) that the 'enabled' boolean controls, providing semantic context beyond the schema's generic 'FX' reference.

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: verbs 'Enable or disable', resource '.icon bundle', and scope 'all Liquid Glass effects... on every group at once'. The phrase 'at once' effectively distinguishes this from the granular sibling set_glass_effects.

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 implied guidance through 'at once' suggesting bulk operations, but lacks explicit when-to-use/when-not-to-use guidance or named alternatives (e.g., does not reference set_glass_effects for individual control).

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