Create event script

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive, but the description adds no behavioral context beyond 'Create'. It does not explain side effects, required permissions, or interaction with the Domoticz system referenced in the cross-link.

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?

While short, the description is overly terse (one sentence) given the tool has 5 parameters and a cross-reference. It sacrifices completeness for brevity, and the cross-reference may require external lookup.

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?

The description fails to provide context for the 'xmlstatement' field, event types, or interpreter options. An output schema exists but its content is absent from the description. The cross-reference partially compensates but is not self-contained.

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 description coverage is 100%, so the parameters are documented individually. The tool description adds no extra semantic meaning; baseline 3 is appropriate as the schema carries the burden.

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 title 'Create event script' and description 'Create script' indicate the purpose of creating an event or script, but lack specificity about what kind of event or what 'script' refers to. It is barely sufficient to distinguish from siblings like 'update_event', but does not clarify scope or output.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'update_event' or 'delete_user_variable'). No prerequisites, contraindications, or contextual triggers are mentioned.

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