mmar_delete_class_instance

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

There are no annotations, so the description carries the full burden. It states the delete action but does not disclose side effects such as whether associated attribute instances, role instances, or ports are also deleted, nor whether the operation requires an active session. This leaves the agent without crucial behavioral information for a destructive operation.

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, clear sentence that gets straight to the point without unnecessary words.

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 simple one-parameter interface and no output schema, the description is mostly adequate, but it lacks details on preconditions (e.g., valid session) and post-conditions (cascade deletes), making it only minimally complete.

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?

The schema already fully documents the only parameter (uuid) with a description and format. The tool description's 'by its UUID' adds no substantive meaning beyond the schema, so a baseline of 3 is appropriate.

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 'Delete' with the resource 'class instance' and clarifies it as 'element/node', distinguishing it from sibling delete tools such as mmar_delete_class and mmar_delete_relationclass_instance. It also specifies the key identifier 'UUID'.

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 clearly indicates the tool's scope: deleting a specific class instance, which implies it should be used over sibling tools like mmar_delete_class or mmar_delete_scene_instance. However, it does not explicitly mention when not to use it or name alternatives, so it falls short of a 5.

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