render_filled_preview

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

Discloses typography approximation and no resource consumption, but does not detail behavior for invalid values or page_index beyond default.

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?

Four brief, well-structured sentences covering purpose, mechanics, cost, limitation, and usage advice; 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?

Provides complete guidance on when and how to use, what to expect, and next step, compensating for lack of annotations and output schema.

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?

Explains values as field-id-to-text mapping with checkbox support, but page_index is left without explanation despite 0% schema coverage.

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?

Clearly states it previews the filled page before PDF generation, explains it draws values into boxes, and distinguishes from fill_pdf.

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?

Explicitly advises to use for verifying placement, alignment, and overflow before calling fill_pdf, and notes no cost/fill consumption.

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