draw

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context about renderer choice and output quality, but says nothing about how the image is produced or where it goes; the presence of an output schema offloads return-value explanation.

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?

It is a single short fragment with zero wasted words, but that brevity comes at the cost of under-specification: there is no leading statement of what the tool does, only a qualifier about the renderer.

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 two-optional-parameter render tool with full schema coverage, annotations, and an output schema, the missing piece is a statement of what it produces and how it relates to ray/png/mpng. The definition is not wrong, just thin for a rendering tool that sits among several rendering siblings.

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 100%, with width and height clearly documented as image dimensions in pixels. The description adds no meaning beyond the schema for either parameter, so the baseline of 3 applies.

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 identifies the rendering backend (OpenGL) and a quality/speed tradeoff, but never states the actual action: that it draws/renders the current scene to an image. An agent must infer the verb+resource from the name 'draw' and from siblings like ray and png.

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 parenthetical '(faster but lower quality)' implies when this tool is preferable over a higher-quality ray-traced render, but it never names the alternative (ray) or states an explicit condition. Usage is implied rather than instructed.

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