hpe_render_verify

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

With no annotations, the description carries the full behavioral burden, yet it only conveys behavioral equivalence to the canonical tool by implication. It discloses nothing about whether the call reads or writes, what it does to the filesystem, permission needs, or side effects.

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?

A single, front-loaded sentence with zero filler. For a pure alias, brevity is the right shape and nothing is padded.

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?

An output schema exists so return values need not be described, but the description does nothing to compensate for zero annotation coverage and zero parameter documentation on a three-parameter tool. An agent still lacks everything needed to call it correctly beyond the alias pointer.

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 all three parameters (pdf_path, page_number, dpi) are undocumented in the schema. The description adds no parameter meaning; only the alias relationship weakly implies the same argument contract as the canonical tool, which an agent must infer.

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 identifies the tool as a backward-compatibility alias and names the canonical sibling it forwards to, which lets an agent place it in the family. However, it never states the actual operation (verifying a rendered PDF page), so the functional purpose is only recoverable by opening hpe_render_clean_verify.

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?

Naming it a 'backward compatibility alias' implies when it would be called (legacy callers) and points at the canonical alternative. It does not explicitly say 'prefer hpe_render_clean_verify for new work' or state any exclusion, so the routing guidance is implied rather than stated.

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