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

Goes well beyond the annotations by disclosing the additive-only constraint on child targets, that workspace restrictions cannot be released from a child, that batch edits are bounded, and that partial failures are reported per item. It still omits auth/permission requirements and any statement about reversibility of removals, so it falls short of a 5.

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?

Front-loaded with purpose, then trigger conditions, then the key constraint, then batch/return semantics. Every sentence carries distinct information with no filler.

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?

Covers the tricky semantics of a multi-mode batch mutation tool (additive child policy, bounded batches, partial-failure reporting), and an output schema exists so return shape need not be explained. Missing only permission/reversibility context for what is a mutation.

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 67% and the schema itself describes target.id, the target type enum, and workspaceId in detail. The description only restates the target types and the additive constraint, adding little parameter-level meaning beyond the structured fields.

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 (Edit) and resource (exclusion policy) plus the exact target scope (workspace, signal agent, workflow). An agent can distinguish this from the read-side sibling campaignstack_get_exclusions without opening the 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?

Explicitly names trigger conditions: add/remove blocked profiles, change filter rules, enable/disable exclusion rules. It does not name an alternative tool or state when not to use it, but the usage context is unambiguous.

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