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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds useful behavioral context beyond that: an 80-item batch cap, that illustrations derive from a reference, and the shell/upload trick to keep the approval prompt short. It does not explain what happens to existing content or what the call returns, so not a 5.

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?

Two tight sentences, front-loaded with the core action and batch limit, followed by the practical upload detail. Nearly every clause earns its place, though the shell instruction is somewhat compressed and dense.

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 3-parameter creation tool with no output schema or rich annotations, the description should close more gaps. It covers the shapes array and upload_id but leaves artboard entirely unexplained, so an agent lacks full guidance to construct a complete call.

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 coverage is only 33%, so the description carries more burden. It names the shape kinds and explains the upload_id workflow in line with the schema, but says nothing about the artboard parameter, which is undocumented in both places, and doesn't clarify shape-item field structure beyond the enum.

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?

States a specific verb (draw/create), resource (shapes, text, paths, pencil strokes), and a concrete capacity limit (up to 80 in one call), which distinguishes it from single-item siblings like pencil or create_path. The 'illustrations are copied from a reference' clause adds scope but is slightly tangential to the core purpose.

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?

Explains a workflow variant (with a shell, upload via curl and pass upload_id) but never states when to choose this batch tool over siblings such as draw_svg, create_path, or generate_illustration. Batch use is implied rather than contrasted with alternatives.

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