elements_create

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

Annotations indicate destructiveHint=true, but the description does not disclose any destructive behavior. It also fails to mention the required expectedRevision parameter, which implies the tool uses optimistic concurrency and may fail if the revision is stale. The description does not contradict the annotations, but it omits critical behavioral context.

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, tightly worded sentence that front-loads the core purpose and immediately clarifies a key constraint ('without accepting XML or arbitrary attributes'). There is zero fluff, and every word contributes to the meaning.

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 tool's complexity—4 required parameters, a detailed schema with 11 shape types, and an output schema—the description is grossly insufficient. It does not mention the required revision parameter, the need for a workspace ID, the types of shapes supported, or any limits on the batch size. An agent would be forced to infer nearly everything from the schema alone.

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 entirely fails to explain the meaning of any of the four required parameters (elements, expectedRevision, path, workspaceId). The description does not even hint at what these parameters refer to, leaving the agent without any semantic guidance beyond the raw 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 the tool's purpose: it 'creates a bounded batch of typed SVG basic shapes'. The verb is specific ('creates'), the resource is defined ('batch of typed SVG basic shapes'), and it explicitly excludes XML or arbitrary attributes, which distinguishes it from potential alternative creation tools. This provides clear intent without ambiguity.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention the sibling tools like elements_update or elements_delete, nor does it explain when this tool is preferable. Without such direction, an agent may struggle to select the appropriate tool among the many element-related options.

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