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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds substantive content-level context beyond that: this inserts a static display table rather than an interactive question, which changes how downstream authoring treats the node.

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 short sentences, front-loaded with the discriminating fact (static table vs question), followed by a type warning and one example. No filler, and the most failure-prone detail (wrong insert type) comes first.

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 7-param mutation tool with no output schema and full schema coverage, the description covers what an agent most needs: what it inserts, what it is not, and the row/col types. Placement behavior (after/position/parentId) is left entirely to the schema, which is acceptable but leaves a small gap for a tool whose default append is noted as 'usually wrong'.

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 the baseline is 3, but the description adds a useful type guardrail ('rows and cols are numbers, never strings') plus a concrete example ({rows:3, cols:2, hasHeader:true}). It says nothing about after/parentId/position semantics, leaving those 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 static content table') and immediately delimits it against the closest sibling by naming editor_insertMatrixQuestion. The parenthetical explaining that cells are author-filled text (not respondent input) makes the distinction 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?

Explicitly gives a when-not-to-use rule ('NOT a question; for rating grids respondents answer, use editor_insertMatrixQuestion'), which is genuine routing guidance. It stops short of covering placement/prerequisite context (parentId, position, formId), which lives only in the schema.

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