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

Annotations already indicate this is destructive (destructiveHint=true) and non-read-only, so the description's 'Remove' adds no new behavioral information. It does not mention irreversibility, cascade effects, or error behavior when the assignment doesn't exist, which would be useful context beyond the annotations.

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?

The description is a single, clear sentence: 'Remove a profile assignment.' It is front-loaded, contains no filler words, and earns its place by restating the action in plain language. For a simple delete tool, this level of conciseness is ideal.

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?

The tool is simple: one parameter, no output schema, and rich annotations (destructive, idempotent, open world). The description, combined with the schema and annotations, provides sufficient context for correct invocation. It could explicitly state that deletion is permanent, but that is already conveyed by the destructiveHint.

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?

The input schema fully describes the only parameter, assignmentId, as a 'Profile assignment UUID,' so schema coverage is 100%. The description adds no additional parameter guidance or edge-case details, but it does not need to because the schema is self-explanatory.

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?

The description uses a concrete verb 'Remove' and a clear direct object 'a profile assignment.' It plainly states the tool's function, and the verb differentiates it from siblings like scoring-assignment-create and scoring-assignment-list, though it does not explicitly name alternatives.

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?

There is no guidance about when to use this tool, when not to use it, or how it relates to other assignment tools. The description simply states the action, leaving the agent to infer usage solely from the tool's name and context.

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