push_rules

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

No annotations are provided, so the description must disclose behavioral traits. It mentions rules run on-device and trigger alerts, but does not reveal important side effects like whether pushing rules overwrites existing rules, validates syntax, requires device online, or may cause repeated alerts. This is a significant transparency gap.

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 two sentences, front-loaded with the action, and every word adds value. No redundancy or filler.

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 tool has moderate complexity with nested rule objects. The description covers the core purpose but lacks details about rule syntax, push behavior (overwrite vs. append), validation, and error scenarios. With no output schema, the description should provide more behavioral context to be fully complete.

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% for top-level parameters (device_id and rules), so the baseline is 3. The description adds meaning to 'rules' by explaining they are JettyScript automation rules for sensor thresholds, but does not elaborate on the individual rule fields (id, when, then) beyond their schema names.

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 tool 'Push JettyScript automation rules to a device' which is a specific verb+resource, and explains the purpose: rules run on-device and trigger alerts on sensor thresholds. This distinguishes it from sibling tools like send_command or get_telemetry.

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 for configuring on-device automation rules, as opposed to one-off commands or telemetry reads. It does not explicitly exclude use cases or compare alternatives, but the context of 'rules run on-device' and 'trigger alerts' provides adequate guidance.

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