get_pvr_finished_id

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

No annotations are present, so the description carries full burden. It lists many error codes, which gives some insight into possible failures, but does not describe core behavior (e.g., read operation, required permissions, output structure). The error codes are listed without context, reducing clarity.

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 short but includes an excessively long list of error codes that dominates the content. The main statement is unclear, and the error list is not organized or summarized. It lacks conciseness and structure.

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?

Despite having an output schema (not shown), the description does not explain the return value. It fails to define 'Frecord' or provide enough context for a simple one-parameter tool. The error codes are the only substantive information, but they are not sufficiently contextualized.

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%, and the description does not explain the 'id' parameter beyond the schema. It does not clarify what the ID represents (e.g., the specific finished recording identifier) or its format.

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 'Returns the requested Frecord' is vague and essentially restates the tool name 'get_pvr_finished_id' without clarifying what an 'Frecord' is. It does not distinguish this from siblings like get_pvr_finished (which likely returns a list) or get_pvr_programmed_id.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where this should be used instead of other get_pvr_* tools.

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