hpe_inspect_virtual_grid

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

With no annotations, the description carries the full burden and does well: it explicitly discloses that it is 'strictly a virtual guide for the agent's eyes; it does NOT alter the PDF', and it documents the returned fields (image path, slot catalog). It stops short of covering lifecycle concerns such as temporary-file cleanup or processing cost.

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 front-loaded and bullet-structured, with the artifact defined first, then overlays, then returns. Every line carries information, including the useful closing NOTE; it is slightly longer than strictly necessary but nothing is filler.

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 describing return values is a bonus rather than a requirement, and the read-only nature is well covered. The remaining hole is total silence on the three input parameters, which for a tool with no annotations leaves an avoidable gap before invocation.

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%, so the description must compensate, and it adds essentially no parameter meaning: pdf_path, page_number, and dpi are never mentioned or explained. A caller gets no guidance on accepted path formats, valid page ranges, or how dpi affects the badge rendering.

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 states a specific verb and resource: 'Generate a temporary Virtual Excel Grid Inspector Image with Set-of-Marks (SoM) slot badges', and even enumerates the overlays it produces. It is clearly distinguishable from a plain render or a fill tool, though it never names a sibling (e.g. hpe_inspect_geometry) to sharpen the boundary.

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?

Usage is only implied: it says to view the output via view_file 'to visually inspect the layout', which hints at a pre-fill inspection workflow. There is no explicit when-to-use vs hpe_inspect_geometry/hpe_snap_fill guidance, and no stated prerequisites or exclusions.

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