hdhomerun_list_recording_rulesLists all DVR recording rules for a household’s DeviceAuth, so you can review scheduled recordings.
List all recording rules for the household's DeviceAuth(s).
| Name | Required | Description | Default |
|---|---|---|---|
| device_auth | No |
Changes observed during successful MCP inspections.
v1.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the scoping note that results span the household's DeviceAuth(s); it says nothing about whether discovery is required first (openWorld) or how results behave when multiple DeviceAuths exist.
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?
One tight sentence with no filler and the resource front-loaded. Efficient, though the brevity is partly the problem rather than a virtue given the undocumented parameter.
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?
A read-only list tool whose annotations cover safety, and no output schema exists so return-shape explanation is less critical. Still, an agent cannot tell from this description how the optional device_auth argument changes the result set, which is the one decision it has to make before calling.
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% for the single optional device_auth parameter, so the description must compensate. It alludes to DeviceAuth scope but never explains the parameter itself: whether omitting it lists rules for all devices, what format the auth string takes, or how results change when it is supplied.
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 (list) and resource (recording rules) with scope qualifier (household's DeviceAuth(s)). Enough to distinguish it from hdhomerun_delete_rule, hdhomerun_add_series_rule, and hdhomerun_change_rule, though it never names those siblings 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?
No guidance on when to call this versus the other rule-related siblings, and no prerequisites or ordering advice (e.g. list before delete). Only the implied 'read' framing from the name carries any usage signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.