create_shape

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

No annotations provided; description fully responsible. It only mentions creation without disclosing behavior like return values, error handling, or side effects. Does not explain what happens if shape_type is invalid or if creation succeeds.

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?

Single sentence that is front-loaded and to the point. No unnecessary words. Earns its place by summarizing the tool's purpose.

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 16 parameters and 5 required, the description provides minimal context. No explanation of 'current canvas', return values, or error scenarios. Output schema missing. Agent likely needs more info to use correctly.

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 100%, so baseline is 3. The description adds no extra meaning beyond summarizing parameters ('position, size, text, and styling'), but does not explain relationships or constraints beyond schema.

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 'Create a shape on the current canvas' with key attributes. It distinguishes from sibling tools like 'create_line' and 'create_node_with_icon' implicitly, but does not explicitly differentiate.

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 on when to use this tool versus alternatives (e.g., 'create_line', 'create_shapes_batch'). No when/when-not context provided.

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