shelly_scene_get

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

The description confirms read-only behavior, which is consistent with the readOnlyHint annotation. It adds value by specifying that the output includes 'ordered actions', which is beyond what annotations alone provide. However, it does not describe error handling or preconditions.

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 very short (one sentence + tag), but it omits critical information about the parameter. It is concise but under-specified, making it less helpful.

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?

Despite having an output schema, the description fails to cover parameter semantics and usage guidance, leaving significant gaps for a tool that retrieves complex data. It is inadequate given the context.

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 0% description coverage, and the tool description does not explain the 'name' parameter (e.g., what it represents or its format). This leaves the agent with no guidance on how to populate the required parameter.

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 verb 'Show' and the resource 'a scene's full definition (its ordered actions)', which distinguishes it from sibling tools like shelly_scene_list (which lists scenes) and shelly_scene_create/delete/run (which modify state). The 'Read-only' tag reinforces its non-destructive nature.

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 does not explicitly state when to use this tool versus alternatives such as shelly_scene_list or shelly_scene_run. While it implies usage for retrieving a scene's details, it lacks contextual guidance on prerequisites or scenarios.

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