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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether renaming is reversible, whether the name must be unique, whether an error is returned for a missing quiz, or what side effects (version bump, updated_at) occur.

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?

A single short, front-loaded sentence with no filler or repetition. It is efficient, though arguably terse to the point of under-specification rather than genuinely 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?

This is a simple two-parameter mutation with no output schema, and annotations cover the safety profile, so a minimal description is nearly sufficient. Still, it omits error conditions and side effects, leaving the agent to assume behavior for a non-idempotent write.

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% (both name and quiz_id are documented in the schema, including the 80-character limit), so the schema does the heavy lifting. The description adds no syntax, format, or constraint information beyond it, making the baseline 3 appropriate.

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 verb and resource ('Переименовывает существующий опрос' = renames an existing quiz), which is enough to distinguish it from sibling mutators like update_quiz_settings or move_quiz. However, it makes no explicit reference to any sibling, so an agent gets no help choosing among the many quiz-mutation tools.

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 gives no when-to-use context, no prerequisites (e.g. must the quiz be unpublished? does the caller need ownership rights?), and no mention of alternatives such as update_quiz_settings. Nothing beyond the bare operation is stated.

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