get_pvr_finished

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

The description provides no behavioral information such as side effects, permissions, or result format. The only content is error codes, which are more relevant to output interpretation than behavior. No annotations exist to compensate.

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 extremely concise (one line of error codes) but at the cost of missing essential information. It is under-specified rather than efficiently informative.

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?

Given the minimal complexity (no parameters, no annotations, no output schema shown), the description should clearly state the tool's function. Listing error codes alone leaves the agent with no understanding of the tool's purpose or return value.

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?

Although there are no parameters, the description adds zero value. It does not clarify that the tool takes no input, nor does it explain the significance of the listed error codes in relation to parameters.

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 only lists error codes and does not state what the tool does (e.g., retrieve finished PVR recordings). It completely lacks a verb or resource specification, making it impossible to discern the tool's purpose.

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 siblings like get_pvr_finished_id or get_pvr_programmed. The error code list offers no contextual clues for usage.

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