hdhomerun_add_datetime_ruleCreate a DateTimeOnly-ChannelOnly recording rule to capture one specific HDHomeRun airing by series, date/time, and channel.
Add a DateTimeOnly-ChannelOnly rule (record one specific airing).
| Name | Required | Description | Default |
|---|---|---|---|
| series_id | Yes | ||
| device_auth | No | ||
| end_padding | No | ||
| channel_only | Yes | ||
| start_padding | No | ||
| date_time_only | Yes |
Changes observed during successful MCP inspections.
v1.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description need only add context. It contributes the rule kind and its effect ('record one specific airing') but says nothing about collisions with existing rules, permissions/device_auth, or reversibility.
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 tight sentence with the key qualifier front-loaded and no filler. Brevity is appropriate, though it leaves too much unsaid for a 6-parameter mutation.
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 mutation tool with no output schema, 0% param coverage, and domain-specific integer/time semantics, the definition is too thin. An agent still lacks the format of date_time_only, the role of series_id, auth requirements, and padding behavior.
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 coverage across 6 parameters, the description must carry all meaning, yet it only names two of them implicitly via 'DateTimeOnly-ChannelOnly'. It omits the date_time_only integer format (epoch? timestamp?), series_id, device_auth, and the start/end padding semantics.
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 (Add) and resource (a DateTimeOnly-ChannelOnly rule) and clarifies with the parenthetical 'record one specific airing'. This distinguishes it semantically from the sibling add_series_rule, though it never names that sibling 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 phrase 'record one specific airing' implies when this tool applies (a single airing versus a recurring series), giving usable context. But there is no explicit when/when-not, no mention of add_series_rule as the alternative, and no prerequisites such as device_auth.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.