Read a HomeyScript script

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds the key detail that it returns the full script code, and specifies the input must match the name from homey_scripts_list. This adds context beyond annotations, though it doesn't disclose additional side effects (none expected).

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?

Two short sentences, front-loaded with purpose, no fluff.

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?

Simple get operation with clear schema and annotations. Description adequately conveys the one parameter and return content. No output schema, but guessing it returns the script object including code is reasonable. Missing exclusions or error cases, but not needed for such a simple tool.

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?

Schema has 100% coverage with description: 'The script id, or its exact name.' The description repeats this and adds the caveat 'as reported by homey_scripts_list', which clarifies usage but doesn't add deep semantics beyond that. Baseline 3 is appropriate.

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 states the tool's specific purpose: 'Returns one script including its code.' It clearly identifies the resource (script) and the action (get/return), and distinguishes from siblings like homey_scripts_list (list all) and homey_script_delete (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?

It provides clear context: takes id or exact name as reported by homey_scripts_list, which guides usage. It doesn't explicitly state when not to use it, but the distinct purpose is clear compared to other script tools.

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