Runn: delete assignment

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

With no annotations provided, the description carries the full burden. It discloses the HTTP method (DELETE) and explicitly states 'hard delete', indicating the action is permanent and irreversible. This is valuable behavioral context, though it doesn't cover return values, errors, or permissions.

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 two sentences with no unnecessary words. It front-loads the primary action and includes the endpoint and hard-delete caveat, making it highly efficient.

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 single-parameter delete tool, the description covers the core action and irreversibility, but lacks information about expected return values, failure modes, or side effects. Given there is no output schema and no annotations, a bit more detail would improve completeness, but it's minimally viable for a simple 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?

The input schema has 0% description coverage, but the only parameter (assignmentId) is self-explanatory. The description adds 'by ID' which maps directly to the parameter, but doesn't provide additional details like accepted formats or constraints. The parameter is simple enough that this is adequate, but not exceptional.

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 clearly specifies the action (Delete), the resource (an assignment), and the method (by ID, DELETE /assignments/{id}). It distinguishes this from sibling tools like runn_create_assignment or runn_delete_phase by focusing on assignments.

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 description implies this tool is for deleting assignments, but it doesn't provide explicit guidance on when to use it versus alternatives or mention any prerequisites. It notes it's a hard delete, which subtly signals it's not for soft-delete scenarios, but this isn't fully elaborated.

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