get_pvr_programmed_id

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

No annotations are provided, so the description must disclose behavior. It only gives a list of error codes and the vague phrase 'Returns the requested Precord'. No information about side effects, permissions, or limitations is given.

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 inefficient. It includes a long list of error codes that should be documented elsewhere. The core purpose is only 4 words, and key information is missing. Not front-loaded with essential details.

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 complexity (many sibling tools, an output schema), the description is completely inadequate. It does not define what a 'Precord' is, how the id relates to the resource, or what the output contains. The error code list is unhelpful without context.

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 schema has one required parameter 'id' of type string, but the description does not explain what this parameter represents (e.g., the PVR record ID). Schema coverage is 0%, so the description should compensate, but it fails to add any meaning.

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 says 'Returns the requested Precord' which is vague and unclear. 'Precord' is likely a typo or abbreviation not explained. There are sibling tools like get_pvr_finished_id and get_pvr_programmed, but no distinction is made.

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. The description only lists error codes but does not explain usage context or prerequisites.

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