streamdeck_read_profiles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List' and 'read_profiles' imply a read-only operation, and the description states what data is returned, but it does not explicitly confirm there are no side effects or describe any runtime behavior like pagination or live-device dependence.

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, compact sentence that immediately states the action, the resource, and the included information. There is no filler or repetition of the tool name.

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 simple no-parameter listing tool with no output schema, the description conveys the key return contents ('profiles with pages, device info, and metadata'). It does not detail the exact response format, but the tool's simplicity and clear scope make this a minor gap.

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 tool has zero parameters and schema description coverage is 100%, so the schema leaves nothing ambiguous. The description does not need to add parameter-level detail, and the baseline of 4 applies.

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 identifies the exact resource ('all Stream Deck desktop profiles') with the fields included ('pages, device info, and metadata'). This clearly differentiates it from siblings like streamdeck_read_page, which targets a single page.

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 phrase 'List all' implies this is the right tool for retrieving an overview of profiles, but there is no explicit guidance on when to prefer this over streamdeck_read_page or streamdeck_manage_profile. For a zero-parameter read tool, the intended usage is reasonably implied.

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