shelly_script_list

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

Annotations already indicate readOnlyHint=true, and the description confirms a read operation with no side effects. The description adds value by disclosing the 'Local-only' constraint and the specific fields returned, which are beyond the annotation coverage.

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 concise—one sentence with a parenthetical list—and front-loaded with the main purpose. Every part is relevant, but the lack of parameter explanation slightly detracts from overall efficiency.

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 presence of an output schema (not shown) and readOnlyHint annotation, the description adequately covers the tool's function and returned fields. However, the missing parameter semantics leaves a gap for a tool with a single required parameter.

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?

With schema description coverage at 0%, the description should explain the single parameter 'device', but it only implies it via the phrase 'on a device'. No format, constraints, or default values are provided, leaving the agent to guess.

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 'List', the resource 'scripts on a device', and specifies the returned fields (id, name, enable, running). The 'Local-only' qualifier distinguishes it from remote operations, and the tool name differentiates it among sibling list tools.

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 implies usage by naming the tool's action, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., when to use shelly_script_list vs shelly_script_get_code). The 'Local-only' hint provides some context but no exclusions.

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