Icon Composer MCP

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

No annotations provided, so description carries full burden. While 'Set' and 'overrides' imply mutation, there's no disclosure of side effects, idempotency, whether unspecified parameters reset to defaults, or persistence 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?

Single efficient sentence, front-loaded with action verb. Every clause serves to scope the operation (appearance modes, target types). No redundancy with schema property descriptions.

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?

Adequate for a setter with high schema coverage, but lacks behavioral depth expected for a mutation tool without annotations. Does not address output behavior or state modification guarantees.

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?

With 100% schema coverage, description adds semantic context by mapping 'appearance' enum to 'dark mode or tinted mode' and 'target' enum to 'icon background fill or layer group', clarifying the domain concepts behind the raw values.

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?

Clear verb 'Set' and specific resource 'appearance overrides' for 'icon background fill or layer group'. Distinguishes from sibling tools like set_fill by specifying 'dark mode or tinted mode' context.

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 guidance on when to use this versus set_fill or set_glass_effects. No mention of prerequisites (e.g., icon existing) or when group_index is required despite schema conditional.

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