read_visual_report

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

No annotations are provided, so the description carries the full burden. The term 'direct artifact directory' hints at a non-recursive or single-level scope, which is useful, but the description does not clarify expected path format, errors, or whether multiple reports are read. As a read operation it is inherently non-destructive, but additional behavioral context would help.

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 a single focused sentence with no filler. The verb and object are placed first, making the tool's purpose immediately understandable.

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?

For a simple one-parameter tool with an output schema, the description is mostly adequate. However, in the context of siblings like read_visual_artifact and compare_visual_runs, the description does not clarify the boundaries between these tools or what 'direct' means in practice, leaving some ambiguity.

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. It does clarify that artifact_dir refers to a 'direct artifact directory' for VisualProbe JSON reports, which adds meaning beyond the bare parameter name. However, it does not specify whether the value should be a path, identifier, or relative/absolute reference.

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 clearly identifies the action (read), the resource (VisualProbe JSON reports), and the scope (one direct artifact directory). It does not explicitly differentiate from siblings like read_report or read_visual_artifact, but the specific 'VisualProbe JSON reports' phrasing provides reasonable distinction.

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?

The description gives no guidance on when to use this tool versus alternatives such as read_visual_artifact, read_report, or list_visual_artifacts. An agent would have to infer the intended use case from the name alone.

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