Delete rule

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known; the description adds no behavioral context beyond that. It says nothing about irreversibility, whether the rule can be restored, or that device authentication may be needed to perform a destructive device operation.

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?

A single dense sentence with the action and both rule families front-loaded; nothing is wasted. The parenthetical combination syntax is compact but readable.

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?

For a destructive, zero-required-parameter tool with no output schema and 0% documented schema, the description covers identification but not authentication, side effects, or result reporting. Adequate to invoke, not complete enough to invoke confidently.

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 0%, so the description must carry the parameter burden. It does explain the valid identifier combinations (RecordingRuleID alone, SeriesID alone, or SeriesID+DateTimeOnly+ChannelOnly), which is genuinely useful, but leaves device_auth completely unexplained and does not clarify the integer type of date_time_only.

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?

States a specific verb (Delete) and resource (Series/Movie rule, DateTimeOnly-ChannelOnly rule), and enumerates the two identification modes. It is clearly distinguishable from the sibling rule tools (add_series_rule, add_datetime_rule, change_rule), though it never names them explicitly.

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 when the tool applies by listing the rule shapes it handles, but gives no explicit guidance on when to prefer hdhomerun_change_rule or hdhomerun_delete_recording, and no prerequisites (e.g. device_auth requirements) are stated.

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