Projects Bulk Delete Assignments

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds valuable non-annotation context: the operation is gated behind an environment flag and an explicit confirm=True. That precondition is exactly the kind of behavior an agent cannot infer from the schema or annotations alone, though irreversibility/partial-failure behavior is not elaborated.

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?

One front-loaded sentence: action and resource first, then the critical gating caveat in parentheses. No filler, no repetition of the title.

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?

An output schema exists, so return-value explanation is not needed, and annotations cover the safety profile. The description supplies the essential gating prerequisite, but for a destructive bulk mutation it stops short of describing atomicity, partial failure, or batch-size expectations.

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 full burden, yet it only sheds light on one of the two parameters (confirm=True required). The required assignment_ids array is undocumented in both places - no batch size limits, no note on the int-or-string item type, no behavior for invalid IDs.

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?

Specific verb ('bulk delete') plus specific resource ('resource assignments'), with the scope qualifier 'multiple' that distinguishes it from the sibling projects_delete_assignment. An agent can tell immediately that this is the batch variant of the single-assignment delete.

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 gating condition ('requires SMARTSHEET_RM_ALLOW_BULK_DESTRUCTIVE=1 and confirm=True') gives a useful precondition for successful invocation. However, it never states when to prefer this over repeated projects_delete_assignment calls or what constraints apply (batch limits), so usage is only implied.

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