Add series rule

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds nothing beyond that: it does not say what happens on a duplicate rule, whether auth is needed, whether the rule takes effect immediately, or how it interacts with existing rules.

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 single sentence is front-loaded and free of waste, but its brevity comes from omitting content rather than being efficiently written. It is concise without being informative.

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 an 8-parameter mutation tool with 0% schema coverage and no output schema, the description is far too thin. An agent would have to guess at padding units, channel/team filter semantics, and auth handling before it could call this correctly.

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% across 8 parameters, and the description only implicitly names series_id. Every other parameter (team_only, device_auth, end_padding, recent_only, channel_only, start_padding, after_original_airdate_only) is left completely undocumented in both the schema and the description.

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 and resource: 'Add a Series (or Movie) recording rule', keyed by SeriesID. This is enough to distinguish it from siblings like hdhomerun_add_datetime_rule and hdhomerun_change_rule without opening the schema, though the sibling differentiation is only implied, not stated.

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?

There is no guidance on when to use this versus hdhomerun_add_datetime_rule, hdhomerun_change_rule, or hdhomerun_list_recording_rules. No prerequisites (e.g., whether device_auth or a reachable device is required) are mentioned, so the agent must infer invocation conditions entirely.

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