Создать или изменить роль

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

Annotations already show readOnlyHint=false and destructiveHint=false, and the description adds useful behavioral context: mutation of existing roles is possible, preset roles are protected from editing, and copy_of enables duplication before customization. This goes beyond the annotations without contradicting them.

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?

Two focused sentences, front-loaded with the core action and then the key exception. No wasted words; every sentence adds useful guidance.

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?

For a create/update tool with 8 optional parameters, the description covers the core behavior and the main non-obvious rule (immutable presets). Given the rich schema, this is sufficient for an agent to call the tool correctly, though a bit more about replacement semantics could have been included.

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 carries the per-parameter meaning. The description adds context around copy_of and presets, but most parameter semantics are already well documented in the schema, so no major compensation is needed.

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 specific action ('заводит роль' / 'меняет существующую') on a clear resource (роль в деле), and it distinguishes itself from roles_delete by covering create/update semantics. The title and description align, and the mention of custom roles vs presets adds precision.

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?

It provides explicit conditional guidance: ready-made roles cannot be edited, and copy_of is the path to customize a preset. It does not explicitly name sibling roles_delete as the deletion alternative, but for create/update usage the context is clear enough.

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