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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows this mutates landscape state and can be retried safely. The description adds role-based authorization context that annotations do not cover, but it does not say whether existing priorities are replaced wholesale or merged, which matters for a destructive batch write.

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 with the action first and the authorization scope in parentheses; nothing is wasted. The parenthetical is dense but still readable, so 4 rather than 5.

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 two-parameter tool with full schema coverage, no output schema, and annotations covering the destructive/idempotent profile, the description is close to sufficient. The one meaningful gap is overwrite semantics for existing priority assessments, which an agent would want to know before issuing a batch write.

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%, and the schema itself documents org_id, node_id, priority enum/null-clears, reasoning, and the size bounds. The description adds only 'in one batch', so the schema does the heavy lifting and the 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 pair (set/clear), the resource (heatmap priorities on the process landscape), and the batch scope, so it is distinguishable from siblings such as setClarityLandscapeNodePlacement or updateClarityLandscapeNode. It does not explicitly name those siblings, which keeps it at 4 rather than 5.

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 parenthetical gives real usage context by stating who may call it (team managers for their own processes; organization admin+ org-wide), which implies scope of use. It never states when to prefer this over a sibling tool or what happens on partial failure, so guidance remains implied rather than explicit.

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