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

Annotations already declare non-readOnly, non-idempotent, non-destructive, openWorld. The description goes beyond them by disclosing a side effect not visible in the schema (email entries can create invitations) and the per-outcome result taxonomy (success, conflict, delivery failure). It still omits auth/permission requirements and partial-failure semantics.

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 sentences, no filler, and the core action and batch scope are front-loaded before the side-effect/outcome detail. Every clause earns its place.

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 batch mutation with no output schema and no annotations covering safety beyond hints, the description gives the action, side effect, and outcome vocabulary, which is a reasonable core. It stops short of batch-size limits, permission requirements, and what happens when some node-person pairs fail, which matter for a 20x20-style bulk operation.

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, yet it only hints at the meaning of the email field (invitations). orgId, nodeIds, and the required per-person fields name, processRole, and teamRole are never explained, leaving most parameters documented nowhere.

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 (Add), resource (people), and target (multiple Process Landscape nodes) with an explicit batch scope. It implicitly separates itself from the singular sibling addClarityLandscapeNodePerson by emphasizing 'one or more people to multiple nodes', but never names that sibling, so 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 phrase 'bounded batch' implies this is the tool for multi-node/multi-person adds, which is usable context, but there is no explicit when-to-use/when-not-to-use guidance and no mention of the singular alternative addClarityLandscapeNodePerson. Usage is implied rather than stated.

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