generate_visual_qa_overlay

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows this is not a pure read operation. However, the description does not disclose the important side effect: writing/overwriting an output PNG file, nor does it explain what is required for correct alignment or what is destroyed.

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 front-loaded sentence with no filler. However, conciseness comes at the cost of under-specification for a 9-parameter tool.

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 9-parameter generation tool with no output schema and no schema parameter descriptions, one sentence is far too thin. It does not explain the output file behavior, grid-point semantics, or how the required overlay inputs relate to one another.

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% across 9 parameters. The description only indirectly evokes pdf_path, page_number, and level_name, and provides no meaning for grid_step_mm, pdf_grid_pt1/pt2, revit_grid_pt1/pt2, or output_png_path. It cannot compensate for the schema's total lack of parameter descriptions.

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 names a specific verb and resource: it overlays modelled elements onto a source PDF page and produces an image for visual QA. That is clear enough to distinguish it from parse_pdf_* and grid-calibration siblings, though 'modelled elements' remains somewhat vague.

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 phrase 'for visual QA' hints at the use case, but there is no explicit guidance on when to use this tool instead of auto_calibrate_grids, parse_pdf_structural_plan, or other sibling tools. No prerequisites or exclusions are stated.

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