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

Goes well beyond the destructiveHint=true annotation by spelling out the blast radius: the node and its proposed descendants are removed, while real processes beneath it survive and are moved back to Unsorted. That side-effect detail is exactly what an agent needs before invoking a destructive, non-idempotent mutation.

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 sentences, front-loaded with the action and scope, then the side effect, then the sibling routing rule. Every sentence carries information an agent would otherwise have to guess.

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 destructive mutation with no output schema, the description covers precondition, deletion scope, survivorship of nested processes, and the sibling alternative. The only untouched field is orgId, which is a minor gap against otherwise complete behavioral coverage.

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 50%: nodeId is documented as 'The proposed node to reject' but orgId is undocumented anywhere. The description reinforces that the target is a proposal but adds no format, scope, or org-context detail, so it neither compensates for the gap nor falls below the baseline for low coverage.

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 (reject/decline) and resource (a proposed process landscape node), and explicitly contrasts itself with deleteClarityLandscapeNode for accepted nodes. An agent can distinguish it from acceptClarityLandscapeNode and deleteClarityLandscapeNode without opening a schema.

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?

Gives an explicit precondition ('while it is still a proposal'), an explicit exclusion ('only proposals can be declined'), and names the correct alternative for the other case (deleteClarityLandscapeNode). Nothing is left to inference.

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