mmar_update_role_instance

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

No annotations are provided, so the description carries the full burden. It only states 'Update an existing role instance' without disclosing prerequisites (e.g., session), side effects, error behavior, or whether changes are reversible. This matches the level of transparency seen in similar under-disclosed mutation tools.

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 two sentences with no redundant words. The first sentence states the action and the second clarifies the exact use case, making it efficient and well-structured.

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 tool's simplicity (2 params, no output schema) and 100% schema coverage, the description adequately covers purpose and usage context. It lacks only notes on side effects or authentication, which would be nice but are not critical for such a targeted update tool.

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 the schema already explains both parameters. The tool description adds a slight semantic hint by linking role_instance_data to the class instance reference, but it does not materially improve on the schema descriptions.

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 names the resource 'role instance', then elaborates that it changes which class instance a connection endpoint references. This clearly distinguishes it from sibling tools like mmar_update_role and mmar_get_role_instance.

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 phrase 'Use this to change which class instance a connection endpoint references' gives clear context for when to use the tool. It does not explicitly state exclusions or alternatives, but the purpose is specific enough to guide selection among similar update tools.

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