add_raw_elements

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

With no annotations, the description carries the behavioral transparency burden. It usefully discloses two non-obvious behaviors: missing version fields are filled in and fractional indices are assigned when absent. It does not mention side effects like merge/replace behavior or return values, but the disclosed normalization details are valuable.

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 efficient sentence that front-loads the action and resource, followed by precise normalization details. Every clause adds information, with no filler or repetition.

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 simple one-parameter action with no output schema, the description covers the essential input semantics and behavior. It lacks explicit sibling differentiation and return-value details, but the low complexity means the description is largely sufficient for correct invocation.

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 0% and the schema only states that 'elements' is an array of objects. The description compensates strongly by specifying the exact expected format: complete Excalidraw elements as represented in an .excalidraw file, and by explaining how missing fields are handled.

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 identifies the action ('Add complete Excalidraw elements verbatim') and the expected source format ('.excalidraw file'), which is specific and unambiguous. It does not explicitly differentiate from the sibling add_elements, though the word 'raw' and 'verbatim' hint at the distinction.

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 implies this tool is for importing exact Excalidraw JSON shapes, but it does not explicitly state when to use add_raw_elements versus add_elements or other siblings. It gives enough context for a reasonable agent to infer the use case, but no direct alternatives or exclusions are provided.

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