streamdeck_list_icons

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

With no annotations provided, the description itself conveys that this is a read-only operation listing available names. 'List' implies no side effects; 'built-in' clarifies scope. It could mention return format or pagination, but for a zero-parameter list tool, this is sufficient.

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 a single, concise sentence that front-loads the action ('List all...') and immediately explains the use context. No wasted words.

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?

For a zero-parameter tool, the description adequately explains what the agent will get: available built-in Lucide icon names. It could specify the return format more explicitly, but the tool's simplicity and clear purpose make it sufficiently 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?

The input schema has zero parameters and 100% schema coverage, so there are no parameter semantics to clarify. The description correctly focuses on the purpose and result rather than parameters.

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 a specific verb ('List') and resource ('all available built-in Lucide icon names'), and explicitly ties it to streamdeck_create_icon. This clearly distinguishes it from sibling tools like read_profiles, write_page, or create_action.

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 description states its purpose: to retrieve icon names for use with streamdeck_create_icon. It does not explicitly say when not to use it, but the context and sibling list make the appropriate use case clear.

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