Icon Composer MCP

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

With no annotations provided, the description carries the full burden. It compensates effectively by disclosing return values ('manifest JSON and list of assets') since no output schema exists. However, it omits safety declarations (read-only nature) and error conditions (e.g., what happens if bundle_path doesn't exist).

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?

The description consists of two efficient sentences with zero waste. It is front-loaded with the action ('Read and inspect') and immediately clarifies the return value. Every word serves a distinct purpose (action, resource, return type).

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 tool's simplicity (single parameter, read operation) and lack of output schema, the description adequately compensates by describing the return structure. It is complete enough for invocation, though mentioning error handling (e.g., invalid path behavior) would achieve full completeness.

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% for the single 'bundle_path' parameter, establishing a baseline of 3. The description reinforces that this path should point to an 'existing' bundle, adding minor semantic context about the file state requirement, but does not add format details or examples beyond the schema.

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?

The description uses specific verbs ('Read and inspect') and identifies the exact resource ('existing .icon bundle'). It clearly distinguishes this tool from mutation siblings like 'create_icon', 'add_layer_to_icon', and 'set_*' tools by emphasizing the 'read' and 'existing' aspects.

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?

While the description implies usage through the word 'existing' (suggesting use for inspection rather than creation), it does not explicitly state when to use this versus 'create_icon' or when to prefer the various 'set_*' and modification tools. No explicit alternatives or exclusions are provided.

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