update_role

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

With no annotations provided, the description burdens all behavioral disclosure. It only states the basic action and does not detail side effects, required permissions, error handling (e.g., role not found), or whether updates are partial or complete. The output schema exists but is not referenced in the description.

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 sentence that front-loads the key information: action, resource, and identifier. It is efficient and avoids redundancy, though it could be slightly more informative without losing conciseness.

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 has a nested object parameter and no parameter descriptions in the schema, the description is insufficient. It does not cover the purpose of the body, expected fields, or whether the update is a full replacement or partial. The output schema exists but is not utilized in the description to indicate return values.

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 0%, and the description does not compensate. It mentions 'numeric ID' for object_id but does not explain the body parameter (an unrestricted object with additionalProperties). No expected keys, constraints, or examples are given, leaving the agent without guidance on how to structure the request.

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 the action ('Update'), the resource ('CDV role'), and the identifier mechanism ('by its numeric ID'). This uniquely defines the tool's function and distinguishes it from sibling tools like create_role, delete_role, get_role.

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 (e.g., create_role for new roles, delete_role for removal). The description lacks any 'when to use' or 'when not to use' context, leaving the agent to infer from the tool name alone.

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