Drawing: Plan (commit intent before drawing)

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

The description explains that the PlanSpec is stored, surfaced for reference, and not replayed as a critique, adding behavioral insight beyond the destructiveHint annotation. It also notes the timing requirement.

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?

Three concise sentences, front-loaded with purpose, each adding value without redundancy.

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 complexity (9 params, well-covered schema, output schema present), the description sufficiently explains the tool's role. Could mention idempotency but adequate.

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 high (89%), so the description does not need to elaborate on parameters. It adds no parameter-specific information, meeting the baseline.

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 tool commits a PlanSpec before geometry creation, with the title adding context. It distinguishes from sibling drawing and entity creation tools by being a preparatory planning step.

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 instruction 'Always call this FIRST in a premium workflow' provides clear usage context but does not explicitly state when not to use or mention alternatives.

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