mmar_update_scene_instance

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

With no annotations, the description carries the full transparency burden. It discloses the smart diffing behavior (new elements added, existing updated) and that new relationclass instances will be created. However, it does not mention potential side effects like deletion of omitted elements or failure modes, leaving a minor gap.

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 concise and front-loaded with the primary purpose, followed by an important usage note and payload requirements. Every sentence adds value; no fluff or redundancy.

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?

The description covers the core purpose, recommended use cases, required payload structure, and key behavioral traits. It lacks explicit mention of return values or error handling, but for an update tool with no output schema, this is a minor omission. Overall it is suitably complete for an agent to invoke correctly.

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?

Although schema descriptions already cover the two parameters at 100%, the description enriches them by specifying the minimum required fields inside the JSON payload (uuid, name, uuid_scene_type) and detailing the relationclasses_instances array structure. This goes well beyond the schema text.

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 opens with a precise verb and resource: 'Update an existing model instance (diagram).' It further clarifies the smart diffing behavior, distinguishing this tool from simple create/delete operations and from the many sibling tools.

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 explicitly states this is the RECOMMENDED way to add connections (relationclass instances), providing a clear use case. It also specifies required payload fields (uuid_scene_type, uuid, name) and the structure for relationclasses_instances, offering actionable guidance.

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