list_livetv_recordings

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

The description adds no behavioral context beyond the annotations: it repeats a read-only GET operation without mentioning scope, pagination, ordering, or any server-side behavior. Annotations already cover readOnly/idempotent/non-destructive, but the description contributes nothing extra.

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 compact and front-loaded, with the purpose followed by the explicit endpoint. It is not bloated, though the first sentence is largely a restatement of the tool name.

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 simple no-parameter read-only tool with an output schema, the description is nearly sufficient. However, it leaves ambiguous whether it returns all recordings globally vs. a specific DVR's recordings, which matters given the sibling get_livetv_dvrs_by_dvr_id_recordings.

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?

The input schema has no parameters and 100% schema coverage, so there is nothing for the description to explain. The baseline for a zero-parameter tool applies.

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?

Description uses a specific verb ('Get') and resource ('DVR Recordings') and gives the endpoint path. It is clear enough, but it does not differentiate this endpoint from the sibling get_livetv_dvrs_by_dvr_id_recordings, which also returns recordings.

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 is provided about when to choose this tool over alternatives such as get_livetv_dvrs_by_dvr_id_recordings or list_livetv_sessions. The agent must infer usage from the name and endpoint path.

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