cavalry_create_layer

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

No annotations exist. Description mentions 'Create' implying mutation but lacks details on side effects, required permissions, or behavior after creation (e.g., selection changes).

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 with ellipsis, no unnecessary words. Could be slightly improved by front-loading the main action, but effective.

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 create tool with 2 params and no output schema, the description is sufficient but minimal. Lacks information on the result of creation, selection state, or error conditions.

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 provides 100% coverage with descriptions. Description adds example type IDs ('textShape, null, colorPlane, ...'), adding value beyond schema. However, no constraints or valid values for 'layerType' beyond examples.

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 'layer by type ID', with example types. It distinguishes from sibling creation tools by specifying 'by type ID', but not fully differentiating from 'cavalry_create_primitive'.

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 like 'cavalry_create_primitive' or 'cavalry_duplicate'. No prerequisites or context provided.

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