cancel_sage_session

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

The description openly states that it cancels running computations and restarts the worker, which makes the destructive nature clear. However, it does not disclose potential side effects like loss of session state or whether prior variables are cleared, leaving some ambiguity for an operation that is likely disruptive.

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?

A single sentence conveys the entire purpose with no filler. Every word adds meaning, making it highly concise and well-structured.

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 cancel tool with zero parameters and an output schema, this description is minimally sufficient. However, it lacks context about when to use it (e.g., when a computation is stuck) and does not differentiate it from the similar sibling reset_sage_session, so complete understanding would require external knowledge.

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 tool takes zero parameters and the schema fully covers this. With no parameters to describe, the description need not add parameter-level detail, so the baseline for zero parameters 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?

Description uses explicit verb 'Cancel' and identifies a specific resource ('running Sage computation') plus the additional effect of restarting the worker. This clearly differentiates it from sibling tools like reset_sage_session, which implies a broader reset rather than just canceling an ongoing computation.

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?

No guidance is provided about when to use this tool versus alternatives such as reset_sage_session or evaluate_sage_streaming. The description does not mention whether this should be used for hung computations or if there are any prerequisites.

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