tldraw_update_shape_props

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

No annotations are provided, so the description must disclose behavioral traits. It mentions it is low-level and to use with caution, but does not explain potential consequences (e.g., breaking references, bypassing validation) or what happens with invalid properties.

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?

Two concise sentences with no wasted words. Each sentence serves a purpose: stating the function and a caution. Front-loaded with 'Low-level' sets context.

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 no annotations, no output schema, and a nested object parameter, the description is incomplete. It lacks information about return values, error handling, and the effects of setting arbitrary properties. Among many siblings, more context for selection is needed.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema; the schema already states 'Properties to set (merged into existing props)' and 'Shape ID'.

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 it directly sets any properties on a shape's props object, using 'low-level' to hint at its generic nature. However, it does not explicitly differentiate from specific sibling tools like tldraw_set_opacity or tldraw_restyle_shapes.

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 only says 'Use with caution,' which is minimal guidance. It provides no explicit direction on when to use this tool vs alternatives (e.g., tldraw_restyle_shapes), nor when not to use it.

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