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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description earns credit for the additions it does make: the owner/admin authorization requirement and the practical retry contract for idempotency_key. It leaves unclear whether omitted fields are preserved or cleared, which matters for a partial-update style 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?

Everything fits in a single front-loaded sentence with no filler; the permission scope and idempotency rule are appended as compact parentheticals. The nested parenthetical referencing "its Edit" is slightly awkward to read but costs no length.

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 six-parameter mutation with idempotency and no output schema, the description covers identity, permission, and mutation fields, but omits the two things most likely to cause a bad call: whether unspecified fields are overwritten and how choices must be shaped (including the correct-answer constraint). Adequate but with clear gaps.

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 only 17%, so the description carries most of the burden. It usefully explains where question_id comes from and names the four editable content fields, but adds nothing about the choices array structure (2-8 items, keyed entries, is_correct flag) or which fields are optional — the most error-prone part of the payload.

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 names a specific verb and resource ("Edits a quiz question") and enumerates the mutable fields (question_text, choices, explanation, image_url), which lets an agent distinguish it from add_training_question and delete_training_question. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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 gives concrete preconditions: the caller must hold an owner or admin seat, and question_id must come from reading training_modules with module_id. It also tells the agent to reuse the same idempotency_key on retries. What is missing is any explicit routing guidance versus edit_training_module or generate_training_questions.

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