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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is covered. The description adds one genuinely new behavioral fact ('May return `needs_confirmation`'), but leaves it unexplained — what triggers it, what to do next, or how approvalId relates — so the added signal is thin.

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, well-ordered sentences with the core action front-loaded; nothing is padded. The final sentence is a dangling fact that would earn more weight if tied to the tool's parameters, but the overall size is appropriate for a small mutation tool.

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 6-parameter destructive mutation with no output schema and 33% schema coverage, the description is too sparse. It omits any explanation of the approval flow implied by approvalId, the required fieldId/nodeId pairing, and the effect of clearing a pin or color — leaving the agent to infer the risky parts.

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 only 33% (color and workspace documented), so the description must compensate for fieldId, nodeId, pinned, and approvalId — all undocumented. The description references 'pinned state' and 'color tag' in prose but adds no format, defaulting, or clearing semantics, and never links the dangling `needs_confirmation` mention to the approvalId parameter.

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?

Specific verb+resource: setting pinned state and/or a color tag on a node, with the useful gloss that pins form the cross-field shortlist. It clearly describes the mutation, though it does not name or distinguish itself from any sibling (e.g. prism_nodes_expand, prism_fields_update).

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives for tagging/pinning. The one contextual line ('Pins are the cross-field shortlist') clarifies the domain concept of a pin but does not tell the agent when this tool is the right call versus another Prism node operation.

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