drawing_create

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

With no annotations provided, the description must fully convey behavioral traits. It states the tool creates a drawing but does not disclose any side effects, permission requirements, validation behavior for SVG input, or interactions with project_id or z-layer. The description is too brief to be transparent.

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, efficient sentence that conveys the core functionality without any extraneous words. It follows the principle of being appropriately sized and front-loaded.

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 the lack of annotations, 5 parameters with 0% schema coverage, and the presence of an output schema, the description is incomplete. It does not explain the purpose of 'z' and 'project_id', nor does it provide any context about expected project state or constraints. The output schema mitigates the need for return value documentation, but the parameter gaps remain.

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 explain all parameters. It covers 'svg' (SVG string) and partially 'x' and 'y' (canvas position), but fails to mention 'z' (likely z-order) and 'project_id'. This leaves 2 out of 5 parameters undocumented in a meaningful way.

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 clearly states the verb 'create' and the resource 'drawing', and specifies the inputs: SVG string and canvas position (x, y). This distinguishes it from sibling tools like drawing_delete and drawing_update, which handle different operations.

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 provided on when to use this tool versus alternatives such as drawing_update or node_create. There is no mention of prerequisites, context, or scenarios where the tool should not be used.

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