Stop a restore session

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

The description discloses the tool's action (stopping a restore session) and provides practical examples. However, without annotations, it lacks details on potential side effects, required permissions, or conditions for success (e.g., that the session must be in-progress). The description is adequate but not exhaustive.

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, concise sentence that includes the verb, resource, and illustrative examples. Every word contributes value, and there is no redundancy or fluff.

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 simple tool with one parameter and no output schema, the description provides sufficient context to understand its purpose and usage. It could be improved by briefly mentioning the expected outcome or that the session must be in progress, but it is largely complete.

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 already provides a detailed description for 'sessionId' ('Restore session ID (GUID) from list_restore_sessions'), which is the only parameter. The tool description does not add any information beyond what the schema already states, so with 100% schema coverage, the baseline score of 3 is 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?

The description clearly states the verb 'Stop' and the resource 'restore session', and provides concrete examples ('cancel a mount / Instant Recovery publish'). It is specific enough to distinguish from sibling tools like 'stop_session', which likely handles other session types.

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 indicates when to use this tool: to stop an in-progress restore session. The examples clarify typical use cases. However, it does not explicitly state when NOT to use it (e.g., for completed sessions) or mention alternatives among sibling tools.

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