Cancel Async Session

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states the tool terminates a session, which implies a destructive action, but it does not mention whether this is reversible, what side effects might occur, or any permission requirements. The optional signal parameter is mentioned but its effect on behavior is not explained.

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 front-loads the action and resource. Every word earns its place, and there is no redundant or filler content.

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 description adequately covers the core action for a simple tool, but gaps remain: it does not explain the return value, error conditions, or the meaning of the optional signal parameter. Given the absence of an output schema and annotations, a bit more detail would make it 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?

Schema description coverage is 0%, so the description must compensate. It names session_id and signal, but does not explain what signal values are valid, what the default behavior is when signal is omitted, or how session_id is obtained. The description adds minimal meaning beyond the schema's bare property names.

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 uses the specific verb 'Terminate' with the resource 'running async session', making the tool's purpose unambiguous. It also clearly distinguishes itself from sibling tools by focusing on the cancellation aspect, especially since there is no other cancel-like sibling.

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 implies when to use the tool (to cancel a running async session) but does not explicitly mention alternatives or exclusions. It does not reference sibling tools like get-result or write-stdin, leaving the guidance to be inferred from context.

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