update_role

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

The description explains the append parameter's behavior but does not disclose side effects, permission requirements, or error handling. Since no annotations are provided, the description carries the burden, but it lacks details on the mutation process.

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 efficient, consisting of one sentence followed by a clear list of parameters. It is well-structured and front-loaded with the purpose.

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 is simple and the description covers the main operation. With an output schema present, return values need not be explained. However, it omits prerequisites like the role needing to exist, but overall it is adequate for the tool's 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?

The description adds meaning to all three parameters: roleid is described as 'Role ID,' privs as 'Comma-separated list of privileges,' and append as 'Append privileges instead of replacing.' This is valuable given 0% schema description coverage.

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 'Update role privileges,' specifying the verb 'update' and the resource 'role privileges.' This distinguishes it from sibling tools like create_role, delete_role, get_role, and list_roles.

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?

No guidance is provided on when to use this tool versus alternatives such as update_acl or update_group. There is no mention of prerequisites or when not to use it.

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