draw

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool uses OpenGL and is faster but lower quality, but it does not disclose what the tool does, what side effects it has, or what output to expect. This is minimal insight into the actual behavior.

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 consists of a single short sentence with no filler words. It is front-loaded with the key technical detail about the OpenGL renderer and the speed/quality tradeoff. While it is under-specified, that is a completeness issue, not a conciseness issue.

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?

Despite having an output schema, the description is very incomplete for a rendering operation. It does not explain what the tool renders, when to use it, or what the result is. Given the complexity of the domain (molecular visualization) and the need to choose between rendering tools, this description is insufficient.

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 provides descriptions for both parameters ('width' and 'height') with 100% coverage, so the schema already documents their meaning. The description adds nothing about the parameters, and per the baseline for high schema coverage a score of 3 is appropriate.

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 only says 'Uses OpenGL renderer (faster but lower quality)' without stating what the tool actually does. It does not explicitly say 'draw an image' or 'render the current scene', leaving the purpose vague. The technical detail about OpenGL hints at rendering but does not define the action or output.

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?

No explicit guidance is given about when to use this tool versus alternatives. The phrase 'faster but lower quality' implies a tradeoff with other rendering methods, but no alternative tools are named and no clear usage scenario is stated. This leaves the decision of when to use 'draw' entirely to the agent.

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