update_graphic

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

With no annotations provided, the description must fully convey behavioral traits. It only states 'Update properties', implying mutation, but fails to disclose side effects, permissions, error conditions, or that it performs a partial update. This is insufficient for safe and correct usage.

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 sentence with no fluff, but it is too brief for a tool with 16 parameters. It is appropriately concise for the purpose but sacrifices important context, making it minimally adequate.

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 the lack of output schema and the large number of parameters, the description is incomplete. It does not clarify that only specified properties are updated, the required 'id' parameter, or the result of the update. The tool's complexity demands more detail.

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 69%, below the 80% threshold, so the description needs to add meaning. It only mentions 'by ID' and 'Update properties', adding no semantics beyond the schema for the 16 parameters. The description does not compensate for the uncovered parameters.

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 'graphic by ID', providing a specific verb and resource. However, it does not differentiate from sibling tools that also act on graphics, such as 'create_shape' or 'delete_graphics', limiting its clarity in a multi-tool context.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or related tools like create_shape for creating graphics, leaving the agent without context for appropriate invocation.

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