render_preview

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

With no annotations, the description carries full burden. It transparently explains the color coding (blue=deterministic, green/orange/red=confidence levels) and that labels show field IDs. It does not address safety or rate limits, but for a preview tool, this behavioral disclosure is sufficient.

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 two concise sentences front-loaded with purpose, followed by necessary details about color coding. Every sentence adds value with no redundancy.

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 preview tool with one parameter and no output schema, the description adequately explains the output (rendered page with boxes), color meanings, and verification purpose. Missing parameter documentation slightly reduces completeness.

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 input schema has one parameter (page_index) with 0% description coverage. The description does not mention page_index or provide any semantic guidance beyond the schema's default value. This is a significant gap as the parameter's meaning is left entirely to the schema.

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 states the tool renders a page with field boxes, with specific color coding distinguishing deterministic vs ML detections. This verb+resource specification is distinct from siblings like fill_pdf or render_filled_preview.

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 implies use for verification of placement via visual inspection, but does not explicitly state when to use or avoid this tool relative to alternatives such as render_filled_preview or list_fields. No exclusions or context for selection are provided.

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