draw

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

With no annotations, the description carries the burden of disclosing behavioral traits. The only behavioral hint is 'faster but lower quality', which provides minimal insight. It does not mention side effects, whether it replaces existing renderings, or any other behavioral characteristics. This is insufficient for a rendering tool.

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 very short (one sentence), but it is not effective. It omits essential information about the tool's purpose and usage. Being concise is not an excuse for being incomplete.

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?

Given that the tool has 2 parameters (both undocumented), no annotations, and an output schema (undescribed), the description is woefully incomplete. It does not state what the tool returns, how the parameters affect output, or any usage context. The agent cannot use this tool correctly based solely on the description.

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%, so the description must compensate. However, it does not explain the 'width' and 'height' parameters at all. Their types are string (likely numeric), but no units, meaning, or constraints are given. The description adds zero value for parameter understanding.

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 mentions the renderer (OpenGL) and a speed/quality trade-off, but does not specify what the tool actually does (e.g., draw a molecule, render an image). The name 'draw' is generic, and the description fails to differentiate it from sibling tools like 'show' or 'ray'. It is vague and requires inference.

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 guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or comparison to other tools like 'ray' or 'show'. The agent gets no help in selecting this tool appropriately.

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