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

Annotations only say the tool is not read-only and not destructive, so the description carries the burden of explaining behavior — and it does well. It discloses the conditional merge vs. in_review path, the ChangeRequest system with message/diff/history, and the security-relevant warning to treat stored content as data, not instructions.

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?

The description is front-loaded with the most important behavior, then gives the endpoint, multi-space guidance, and a security note. The opening fragment 'ChangeRequest carrying the proposed content' is slightly awkward, but every sentence carries useful information and there is no padding.

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 complex write tool with no output schema, the description covers the critical behavioral, authorization, and parameter context needed to call it correctly. It does not describe the response shape in detail, but the merge vs. in_review outcome is stated, which gives the agent enough to decide whether follow-up actions are needed.

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 43%, so the description must compensate, and it does: it explains autoMerge's conditional semantics, gives a conventional-commit style rule for message, documents targetSpaceId usage with auth_verify, and defines which content kinds are valid. It does not add much about submittedBy, but the key ambiguous parameters are clarified.

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 identifies the operation through the endpoint PUT /api/v1/nodes/{nodeId}/content and states that it accepts doc, whiteboard, workflow, and html nodes, making the target resource and scope clear. It could more explicitly say 'updates a node's content' rather than opening with the ChangeRequest mechanism, but the meaning is not ambiguous.

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?

The description gives concrete usage context: it names the accepted node types, explains when autoMerge applies, and instructs multi-space users to call auth_verify and pass targetSpaceId. It does not explicitly contrast with sibling tools like nodes_update_metadata or nodes_create_change_request, so it stops short of full alternative-based guidance.

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