streamdeck_create_icon

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

No annotations are present, so the description carries the behavioral burden. It does disclose the output format, resolution, and the fact that the result is a file path, which is meaningful. However, it does not mention possible side effects like overwriting an existing file, where the file is written, or how conflicting content parameters are resolved.

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 is two concise sentences with high-value information front-loaded: purpose and output first, supported use cases and return value second. It contains no filler or repetition and every phrase carries meaning.

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?

The description explains the core deliverable and return value, which is important because there is no output schema. However, the schema has 14 optional parameters and no required ones, yet the description gives no guidance about defaults, required content selection, or what happens if multiple content sources are supplied. For such a flexible schema, the description is competent but not fully complete.

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?

Every parameter already has a schema description (100% coverage), so the baseline is 3. The tool description adds an extra layer by grouping parameters into supported content modes (text, Lucide icons, app icons, emoji, gradients, badges), which is not obvious from the flat schema and helps an agent choose the intent. It still does not explain exclusivity or combination rules.

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 states a specific action ('Generate'), a precise output ('144x144 PNG icon'), and a return value (file path). It also lists the supported content types, which clearly distinguishes it from sibling tools that read/write pages, profiles, or actions, or list icons.

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?

The list of supported content types (text, Lucide icons, app icons, emoji, gradients, badges) implies when this tool is appropriate, and sibling names confirm it is the icon-creation tool. However, there is no explicit when-not-to-use guidance, no alternatives for fetching or listing icons, and no mention of prerequisites such as needing an existing icon.

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