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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the return is 'raw JSON' and frames the result as a value to merge, which is mild extra context, but it discloses nothing about error behavior for missing nodes or the shape of the returned JSON.

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?

Two short sentences, front-loaded with the core action, with no filler words. However, the second sentence is jargon-dense and grammatically compressed ('propsPatch replaces string props whole'), which costs some readability without adding length.

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 read tool whose annotations fully cover safety and whose schema fully documents both parameters, the description is close to adequate. It is still incomplete on what a node's raw JSON looks like and what happens on an unknown nodeId, and with no output schema the description is the only place that could have hinted at the return shape.

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 description coverage is 100% with only two parameters (id, nodeId), and the schema already supplies examples like ROOT and page_home. The description adds no parameter-level meaning such as which identifiers are valid or how nodeId relates to the site id, so baseline 3 applies.

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+resource: 'Read one node's raw JSON.' The word 'one' implicitly distinguishes it from list_site_nodes and search_site_nodes in the sibling set, but it never names those siblings, so the differentiation is left to inference.

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 second sentence hints at the use case (fetching the current value to merge before patching props), which implies a workflow with patch_site_node, but it never states when to use this tool versus list_site_nodes/search_site_nodes, and the phrasing 'so this is the current value to merge into' is elliptical enough that an agent must decode it.

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