shelly_script_start

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

The description discloses that it returns 'was_running' and is audit-logged, providing some behavioral insight. However, with no annotations, it lacks detail on side effects, error handling, or behavior if the script is already running.

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, front-loaded sentences. Every phrase adds value—no filler. The format is efficient and directly usable.

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 many sibling script tools and an output schema, the description is too sparse. It omits context about the device parameter, return structure, and prerequisites, leaving gaps for an AI agent.

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 0% schema description coverage, the description should add parameter meaning. It only mentions 'id' implicitly but does not explain the 'device' parameter or the format of 'id'. No value beyond the schema is provided.

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 'Start a script by id', which is a specific verb+resource pair. It effectively distinguishes from sibling tools like shelly_script_stop or shelly_script_eval.

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?

While 'Start a script' is intuitive, there is no guidance on when to use this versus alternatives like shelly_script_eval or shelly_script_stop. The mention of 'Audit-logged' hints at tracking but doesn't clarify use cases.

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