delete_assignment

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description still adds real behavioral context: the assignment is removed from the resource and, for access-restricting tags, affected users immediately lose access. It stops short of stating error behavior for a nonexistent assignment or whether the tag itself survives (it does, implicitly).

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 short sentences preceded by the endpoint, with the consequence front-loaded right after the core action. No filler, though the bracketed URI is partly redundant with the parameter set and costs a line.

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 delete with no output schema and full-schema parameter docs, the description supplies what structured fields cannot: the downstream access impact. Minor gaps remain — whether missing assignments error versus no-op, and confirmation that the tag record itself is untouched.

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 100% and the resourceType enum values are documented in the schema, so the schema already carries the parameter burden. The description adds only the path template, which mirrors the same three required identifiers without new semantics; 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 (Delete) plus a precise resource (tag assignment) scoped to a tag/resource pair, and the endpoint template disambiguates it from siblings like delete_tag and create_assignment. An agent can tell exactly which object this removes 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?

Usage is only implied by the verb — nothing states when to prefer this over delete_tag, or that retrieve_assignment_list should be used to find the resourceId first. No exclusions or prerequisites are given, though the sentence about access restrictions hints at when the call matters operationally.

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