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

Annotations already declare this is a non-destructive, closed-world write (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the safety profile is covered by structured data. The description adds the option-count precondition, but says nothing about permissions needed, what happens to the form on failure, or that an element/node id is produced. Adequate, not rich.

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 sentences, no filler, front-loaded with the tool's identity before the routing hint. Every clause earns its place.

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 10-parameter insert tool with a fully documented schema and annotations that already cover the write/safety profile, the description supplies the one piece of context the schema cannot: which sibling to pick when multiple answers are needed. No output schema exists, so return values need not be explained, though noting the created element's id would have been a nice addition.

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% and every parameter (after, parentId, position, isHidden, required, placeholder, randomizeOptions) is already documented in the schema with usage hints such as '$prev to chain' and 'Not combinable with after'. The description's 'Requires 2+ options' merely restates the schema's minItems: 2. Baseline 3 is correct when the schema carries the burden.

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 gives a specific verb ('Insert'), the exact resource ('dropdown select question'), and the semantic scope ('one answer from a list') that separates it from the multi-answer siblings in the editor_insert*Question family. An agent can immediately tell it apart from editor_insertCheckboxQuestion. The only unstated cousin is editor_insertRadioQuestion, which shares the single-answer semantics, but the stated purpose is unambiguous.

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 states an explicit routing rule: 'For several answers use editor_insertCheckboxQuestion,' and gives a precondition ('Requires 2+ options'). It does not address the closer competitor editor_insertRadioQuestion, so the agent must infer select-vs-radio from the name alone. Clear context, but not a full when/when-not matrix.

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