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

The description says 'Sending fields replaces every question,' which describes a destructive replacement of existing form questions. This directly conflicts with the annotation destructiveHint=false, which declares the operation non-destructive.

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 two short sentences with no wasted text. The key replacement warning is front-loaded and easy to act on.

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 mutation tool with five parameters, no output schema, and low schema description coverage. The description covers the core title/questions behavior but omits semantics for two optional parameters and gives no usage guidance relative to sibling tools.

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 20%, so the description must compensate, but it only explains the title and fields/replacement behavior. It says nothing about the optional description or send_to_new_students parameters, leaving important semantics undocumented.

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: it changes the title or questions of an anamnesis form. This is clear enough to distinguish it from create_anamnesis_form and read-only siblings, though it does not explicitly name any alternative tool.

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 usage context is implied by 'Changes the title or questions,' and the warning that sending fields replaces every question is useful. However, it does not explicitly say when to use this versus create_anamnesis_form, toggle_anamnesis_form, or other form-related tools.

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