tvh_list_dvr_profiles

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

Annotations already declare this to be a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds useful context about the kinds of DVR settings returned, but it does not disclose pagination behavior, default limits, or any other execution detail beyond the annotations.

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 a single front-loaded sentence that quickly communicates the tool's resource and included settings. It contains no filler or redundant restatement of the 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?

With an output schema present and annotations covering the read-only safety profile, the description does not need to explain return values in detail. However, it omits pagination semantics and usage guidance for the two undocumented input parameters, leaving the definition minimally adequate rather than fully complete.

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 0% description coverage for both the 'limit' and 'start' parameters, and the description does not mention either parameter or explain their semantics. The parameter names and schema defaults hint at pagination, but the description does not compensate for the missing schema documentation.

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?

The description uses a specific verb ('List') and names the resource ('DVR profiles') plus relevant returned settings such as output directories, padding, and retention. It is clearly distinguishable from the sibling creation tools, though it does not explicitly contrast itself with tvh_create_dvr_profile or tvh_list_dvr_rules.

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 only states what is listed; it gives no guidance on when to use this tool versus alternatives such as tvh_create_dvr_profile or tvh_list_dvr_rules. There are no prerequisites, exclusions, or contextual cues for selecting this tool.

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