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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real value on top by disclosing that nodes are unaffected by the edit, that passing null reverts the name to the origin idea, and that the call may return a needs_confirmation envelope. It stops short of describing what the confirmation flow requires or whether changes are reversible.

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 operation and immediately followed by the most decision-relevant constraint (nodes untouched). No filler or restatement of the title.

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 destructive mutation with no output schema, the description covers scope, the null-revert rule, and the confirmation handshake. Missing details are minor: what triggers needs_confirmation, and what the call returns on success, though the annotation already flags destructiveness.

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 67%, and the description fills the notable gap: the bare 'name' property has no schema description, and the text explains that null reverts to the origin idea. The needs_confirmation mention also contextualizes the otherwise cryptic approvalId parameter. Visibility semantics are left to the schema's own enum description.

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 (edits) plus the exact editable attributes (name, description, visibility) and scopes the blast radius with 'Nodes are untouched', which cleanly separates it from prism_nodes_update and from prism_fields_create/delete. An agent can identify the operation 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?

Implies usage by pointing at prism_fields_list as the source of field ids and by warning that a needs_confirmation envelope may come back, but it never states when to prefer this over prism_fields_create/delete or what preconditions must hold. Usage is inferable rather than explicit.

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