ae_create_shape

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

No annotations are provided, so the description carries the burden. It states that position is the layer's transform position and geometry is drawn around it, which gives some insight. However, it does not disclose side effects, required permissions, or behavior when parameters are omitted. For a tool with no annotations, more transparency is expected.

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 two sentences, front-loading the purpose with a clear verb and examples. It is efficient with no wasted words, though it could be slightly expanded to cover behavioral aspects without becoming verbose.

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?

With 7 parameters and no output schema, the description is too sparse. It does not explain default behaviors, parameter interactions (e.g., roundness only for rect), or what is returned. The tool's complexity demands more complete context.

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 71%, so baseline is 3. The description adds that the shape geometry is drawn around the position, but otherwise repeats information already in the schema. It does not add significant meaning beyond the schema's own descriptions.

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?

Description clearly states it adds a shape layer (rounded rectangle or ellipse) with solid fill, and gives concrete examples (UI button, background frame). It distinguishes from siblings like 'ae_create_solid' by focusing on geometry, 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?

The description provides basic usage context ('e.g. UI button or background frame') but does not specify when not to use it or mention alternatives such as 'ae_create_solid'. No explicit guidance on choosing this over sibling tools.

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