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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds genuine value by disclosing that the delete is a SOFT delete (implying the record may be recoverable rather than purged) and naming the auth scope required. It stops short of saying whether the action is reversible or what it cascades to.

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 with zero filler, and the soft-delete qualifier is front-loaded right after the verb where it matters most.

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 destructive mutation this is nearly complete: the annotations carry the safety signal, both params are fully documented, and the description supplies the soft-delete nuance and auth requirement. It omits downstream effects (e.g. impact on bookings or photos tied to the room), which would have rounded it out.

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 both parameters are already documented, including the pointer to getMyStayRooms for roomId. The description adds no parameter-level meaning beyond that, so the 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 and resource ('Delete (soft-delete) a room from a Stay'), and the 'from a Stay' scoping plus the room/photo distinction separates it from siblings like deleteRoomPhoto and deleteStayPhoto. An agent can pick this tool 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?

It gives a prerequisite ('Requires an MCP agent token scoped to the owning account'), which is real usage context, but offers no when-to-use vs when-not guidance or any named alternative. Usage is only implied by the destructive verb.

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