agent_cancel

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

Annotations already indicate readOnlyHint=false (a write operation) and destructiveHint=false (not destructive), but the description adds no detail about side effects, irreversibility, or what 'cancel' actually does to the session. Since annotations are minimal, the description should disclose more behavioral context.

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, front-loaded sentence with no fluff. It is economical, but the extreme brevity contributes to under-specification elsewhere. Still, for what it contains, it is 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 cancellation tool with no output schema and sparse annotations, the description is too thin. It leaves an agent guessing about consequences, required parameter formats, and how this relates to other session-management tools. The context is not complete enough for safe invocation.

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 for the two parameters (provider, nativeId). It fails to explain what 'nativeId' means or what valid provider values are beyond the enum values in the schema. The phrase 'provider native session' hints at provider but adds no concrete parameter semantics.

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 identifies the action verb 'Cancel' and the resource 'work in a provider native session'. It is specific enough to distinguish from major siblings like stop_thread (which targets a thread) and session_create, though 'provider native session' is somewhat jargon-heavy.

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 on when to use this tool versus alternatives like stop_thread or resume_thread. The description does not mention exclusions, prerequisites, or scenarios where cancellation is appropriate.

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