Abort Wiki upload session

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

Annotations already carry destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is known. The description adds real value beyond that: it specifies that uploaded parts are discarded, quota is freed, the session cannot be resumed, and the returned status is 'aborted'.

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 tight sentences with the action and scope front-loaded, followed by the consequences and return status. No filler or redundancy.

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 destructive operation, the description plus annotations cover what the agent needs: what is destroyed, that it is irreversible, and the returned state. No output schema exists but the return value is described inline.

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 100% (session_id documented as a UUID4), so the schema already does the work. The description adds no additional parameter syntax or format detail, making the baseline 3 appropriate.

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 (abort/cancel) and resource (upload session) with a scoping qualifier ("one in-progress upload session") that distinguishes it from the sibling wiki_uploadsessions_abort_all. An agent can tell exactly which session is targeted.

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 implied by the purpose (cancel a session you no longer want), and the irreversibility note gives context, but the description never states when to abort versus finish or abort_all, nor any prerequisite such as session ownership.

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