create_excalidraw

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

With no annotations, the description carries the full burden of explaining side effects and requirements, but it only says a drawing is created. It does not mention overwrite behavior, required permissions, file system effects, or any other behavioral consequences.

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 short and free of filler, which is positive. However, it is under-specified rather than efficiently informative, omitting context that would make the single sentence genuinely useful.

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?

A create operation with three optional parameters, no annotations, and no parameter documentation needs more context to be complete. The output schema may describe return values, but the description still leaves the agent guessing about folder and subpath semantics and about when this tool is appropriate.

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%, and the description does not mention the title, folder, or subpath parameters at all. The agent gets no help understanding what these parameters mean or how they affect the created drawing.

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 action and resource: 'Cree un dessin Excalidraw' (create an Excalidraw drawing). This identifies the tool's purpose and distinguishes it from siblings like create_note or create_folder. However, it is very close to a restatement of the tool name and provides no further detail.

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 gives no guidance about when to choose this tool over alternatives such as create_note, upload_asset, or other creation tools. There is no context, prerequisite, or exclusion information.

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