update_element

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

Since there are no annotations, the description carries the full burden of disclosing behavioral traits. It only states that it updates an existing element, but does not mention side effects (e.g., overwriting vs. merging), error behavior if the id does not exist, or any permissions required. This is a significant gap for a mutation tool.

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, succinct sentence with no fluff or redundant wording. It is front-loaded and easily parsed. However, its extreme brevity sacrifices essential explanatory content, which slightly detracts from its structural effectiveness.

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 tool with 15 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to convey what properties are updatable, whether the operation is a partial or full replacement, and what the expected return value or side effects are. The tool's complexity is not matched by the descriptive 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?

With 0% schema description coverage and a 15-parameter schema, the description is required to compensate, but it does not explain the meaning or use of any parameter beyond the implicit understanding that 'id' identifies the element. There is no mention of how x, y, text, or other properties are applied, making the parameter semantics entirely ambiguous.

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 ('Update') and the resource ('an existing Excalidraw element'), which distinguishes it from sibling tools like create_element and delete_element. However, it does not elaborate on what aspects of the element can be updated, so it lacks some specificity.

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 no guidance on when to use this tool versus alternatives like create_element or lock_elements, nor does it mention any prerequisites or contexts. There is no explicit exclusions or favored scenarios, leaving the agent to infer usage solely from the tool name.

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