update_shape

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

With no annotations, the description carries the full burden of behavioral disclosure but only says 'Update shape properties,' which vaguely implies mutation. It doesn't state whether unspecified properties are left unchanged or reset, whether some properties only apply to text shapes, or what the response contains. This is a significant gap for an update 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, front-loaded sentence with a clear verb and object, and the property list is relatively concise considering the large schema. There is no redundant or filler content.

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 49 parameters and no annotations or output schema, the description should clarify update semantics (e.g., partial update), shape-type applicability of certain properties, and required identifiers, but it doesn't. This leaves substantial ambiguity for the agent.

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?

All 49 properties already have schema descriptions, so the baseline is 3. The description's property list merely summarizes what the schema already details, adding no extra meaning about parameter interactions, constraints, or partial-update behavior.

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 uses the specific verb 'Update' and identifies the resource ('shape properties') with a comprehensive list of property categories, making it clear this modifies existing shapes. It distinguishes itself from creation tools like create_rectangle and read tools like get_shape_properties.

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 the tool is for modifying existing shape properties but provides no explicit guidance on when to prefer it over related tools like align_shapes or distribute_shapes, nor any exclusions. The verb 'Update' gives a clear basic context, but no alternatives or when-not-to-use scenarios are mentioned.

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