reset_compute_session

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

Beyond the annotations (destructiveHint, idempotentHint), the description adds valuable behavioral context: the server keeps a reusable session per user/context, state persists across execute_sas_code and list_compute_* calls, and the next call transparently creates a fresh session. This explains the consequences of resetting without contradicting 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 four sentences, front-loaded with the action, then providing necessary context about the session reuse model and the effect of calling reset. Every sentence contributes meaning without 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?

The tool has a single optional parameter, well-documented in the schema, and an output schema exists (per context signals). The description fully explains the tool's purpose, the persistence behavior, and the consequence of resetting, making it complete for an agent to decide when and how to invoke it.

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 schema already fully describes the only parameter (compute_context_name) with 100% coverage, including its default behavior. The tool description does not add any parameter-specific details, so the baseline of 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?

The description opens with a specific verb+resource: "Reset (delete) the cached compute session for a compute context." It clearly distinguishes this tool from its siblings by explaining it discards persisted SAS session state, which is unique among the listed compute-related tools.

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 explains when to use the tool: "Call this to discard that state" after detailing the persistence mechanism. It provides clear context about the session caching behavior and the effect on subsequent calls, but it does not explicitly name alternative tools or state when not to use it. However, the usage context is unambiguous.

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