delete_pvr_finished_id

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing side effects, irreversibility, permissions, or what 'associated files' entails. The error code list offers some hints about failure modes but does not describe expected behavior.

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 very short, but the inclusion of a long error code list is somewhat cumbersome and not structured. The core action is stated upfront, but the error codes could be explained or placed in a separate field.

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 only one parameter and an output schema (not shown), the description lacks details about return values, irreversibility, and potential side effects. The error codes are present but not contextualized. A more complete description would clarify what is deleted and the implications.

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 single parameter 'id' is not described in schema (0% coverage). The description does not elaborate on what 'id' represents, but the tool name suggests it is the finished PVR record ID. For a simple required string, this is minimally adequate.

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 clearly states 'Delete a Frecord and associated files', which aligns with the tool name indicating deletion of a finished PVR record. It is distinct from sibling tools like delete_pvr_programmed_id, though it does not explicitly mention 'finished' in the description.

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 usage guidance is provided. The description does not specify when to use this tool over alternatives, nor does it mention prerequisites or conditions. The long list of sibling delete tools further highlights the lack of differentiation.

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