shelly_script_put_code

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

The description adds value beyond the destructiveHint annotation by detailing chunking, append behavior, and audit logging. It does not contradict annotations and provides useful context about the confirm flag and arbitrary code execution.

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 concise at three sentences, uses bold for emphasis, and has a clear structure. Every sentence adds value without unnecessary verbosity.

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 output schema exists, the description appropriately focuses on input behavior. It covers critical aspects like chunking, append modes, and the confirm safety flag. Minor gaps include lack of mention of script existence prerequisites.

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 explains the 'append' and 'confirm' parameters and their implications. However, it omits explanation for 'id' and 'device' parameters, which are required and could be clarified.

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 action (upload code), the resource (script), and mentions chunking and the confirm flag. It distinguishes from siblings like shelly_script_get_code and shelly_script_create.

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 explains chunking and append behavior but does not explicitly state when to use this tool vs alternatives such as shelly_script_eval or shelly_script_create. Usage context is implied but not explicitly defined.

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