crm_update_role

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

With no annotations, the description carries full burden for disclosing behavioral traits. It only says 'Update role details' with no mention of permissions, reversibility, partial vs. full replacement of role_data, or what the response looks like. This is a significant gap for a mutation 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 concise (a single sentence) and front-loaded with the action. However, it is overly minimal and lacks useful context, making it under-specified rather than appropriately sized. It earns its place but leaves significant gaps.

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 tool has nested objects (role_data) and no output schema, and annotations are absent. The description is far too incomplete to guide an agent: it fails to mention updatable fields, validation, partial update behavior, or any response expectations. This is inadequate for a mutation tool of this complexity.

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% with both parameters having descriptions, so baseline is 3. The description adds no extra meaning beyond the schema; it doesn't explain the structure of role_data or any constraints. However, the schema descriptions are minimally present, so the parameter semantics are adequately covered by schema alone.

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 states a clear verb and resource: 'Update role details'. It distinguishes from sibling tools like crm_create_role, crm_delete_role, and crm_get_role_details by indicating a modification operation. However, it does not specify the exact scope of 'role details', which is slightly vague.

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 that this is for updating existing roles, or that creation/deletion should use other tools. The usage is only implied by the name and verb, but no explicit context or exclusions are provided.

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