update_livetv_dvrs_by_dvr_id_lineups

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

The description contains an annotation contradiction: it describes the lineup parameter as 'the lineup to delete', which implies destructive behavior, while the annotations declare destructiveHint=false. It also adds no useful behavioral context beyond the annotations, such as idempotency effects or what happens to existing lineups.

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 text is short and has an Args section, but the incorrect 'to delete' wording is actively harmful, and the HTTP path is redundant with the tool name. Not every sentence earns its place.

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 two-parameter tool, the description should be easy to follow, but the conflicting parameter description makes it incomplete. The presence of an output schema reduces the need to explain return values, but the core semantics of what 'lineup' should contain are missing.

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%, so the description must carry the parameter semantics. 'dvr_id: The ID of the DVR' adds little beyond the property name, and 'lineup: The lineup to delete' is likely a copy-paste error from the delete sibling, making the actual value expected for an add operation unclear.

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 opening phrase 'Add a DVR Lineup' is a specific verb plus resource, and the HTTP path matches. However, the parameter explanation later says 'The lineup to delete', which directly contradicts the stated purpose and leaves the agent uncertain whether this tool adds or removes a lineup.

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 about when to use this tool versus the sibling delete_livetv_dvrs_by_dvr_id_lineups or the various DVR update tools. It simply states the operation without giving context, prerequisites, or exclusions.

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