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

Annotations declare the safety profile (readOnly=false, destructive=false, openWorld=false), so the agent knows this is a non-destructive create. The description adds a real behavioral gotcha beyond annotations: rows/columns must be native string arrays and never a JSON string. It does not mention permissions or insertion side effects, so not a 5.

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?

Three tight sentences, front-loaded with purpose, then usage, then the param constraint and a compact example. Every sentence earns its place and the example is illustrative rather than filler.

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 9-param creation tool with no output schema and safety covered by annotations, the description gives purpose, usage, and a concrete example. It omits the ordering/chaining semantics (after, position, parentId), but those are documented in the schema, so it is largely complete.

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 coverage is 100%, so baseline is 3. The description exceeds it by illustrating the shape of the key params (title/rows/columns) and flagging the native-array-vs-JSON-string pitfall. It leaves the ordering params (after, position, parentId) to the schema.

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?

States a specific verb and resource ('Insert a matrix/grid question') and clarifies the matrix/grid concept that distinguishes it from the ~25 sibling editor_insertXQuestion tools. An agent can identify it without opening the schema.

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?

Gives clear usage context ('Use when rating multiple items on the same scale'), which separates it from a plain rating question. However, it names no explicit alternative or exclusion (e.g., vs editor_insertRatingQuestion or editor_insertLinearScaleQuestion) for the borderline grid-vs-scale case.

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