shelly_scene_list

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

The description adds 'Read-only' which reinforces the existing readOnlyHint annotation. It does not provide additional behavioral details beyond what annotations already convey, such as any side effects or access requirements, but is consistent.

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 extremely concise with two sentences. It front-loads the primary purpose ('List defined scenes') and adds only relevant detail about returned fields. No extraneous content.

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 has no parameters, an output schema exists, and annotations provide safety information, the description is complete enough. It specifies the output fields, making it sufficient for an agent to understand the tool's capability.

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 no parameters, and schema coverage is 100% (vacuously). With zero parameters, the baseline is 4, and the description adds no parameter information because none is needed.

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 clearly states the tool lists defined scenes and specifies the included fields (name, description, action count). This distinguishes it from sibling scene tools like shelly_scene_get, shelly_scene_create, shelly_scene_run, and shelly_scene_delete.

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 indicates a listing operation with 'List defined scenes' and emphasizes it is read-only. While it does not explicitly mention when to avoid this tool, the context and sibling names make the usage clear for a simple list operation.

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