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 genuinely new behavioral context beyond annotations: the role-based authorization requirement, which differs by node type (team process vs area) and is not present in the structured fields.

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?

A single front-loaded sentence states the action before the parenthetical permission qualifier, with no filler. The nested parenthetical is slightly dense to parse but every clause earns its place by adding an authorization rule.

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 simple two-field mutation with no output schema, the description covers the action, the fields, and the permission gate. It stops short of explaining null-clearing of ownerLabel or the interaction with placement siblings, but the annotations and schema carry enough that an agent can call it correctly.

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 0%, so the description carries the burden. It names the two mutable fields ('name' via rename, 'ownerLabel') and clarifies that ownerLabel is a team/area ownership label, but adds nothing about orgId/nodeId semantics and does not explain that ownerLabel accepts null to clear it.

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 gives a specific verb pair ('Rename ... or update its owner label') against a precise resource ('process landscape node'), so an agent knows exactly which fields this mutation targets. It implicitly distinguishes itself from siblings like setClarityLandscapeNodePlacement and updateClarityLandscapeNodePerson, but never names them explicitly.

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?

It supplies a use condition in the form of permissions ('team manager or above for team processes; organization admin for areas'), which tells the agent whether the caller is likely authorized. However, it never contrasts this tool with the adjacent siblings (placement, person updates) or states when not to use it, leaving the alternative-routing decision to inference.

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