pi_abort

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

With no annotations, the description carries the full burden. It usefully discloses that the session remains alive and messages can still be sent, but it does not explain what happens to the aborted operation, whether the action is idempotent, or any side effects on the task's state.

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 two short sentences with no filler. The action is front-loaded, and the key consequence of using the tool (session stays alive) is stated immediately and clearly.

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 one-parameter control tool, the description covers the most important distinction from sibling tools, but it omits parameter semantics and what happens after the abort completes. Since there is no output schema, more detail about the response or state would improve completeness.

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%, and the description does not mention taskId at all. The schema only says it is a required string, so the agent receives no additional meaning about what the parameter represents or how it should be obtained.

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 a specific verb ('Abort') and resource ('the pi task's current operation'), and immediately differentiates from siblings by noting the session stays alive, so it is clearly not a full session teardown like pi_close. This makes the tool's purpose unambiguous.

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 usage context: use this to abort the current operation while keeping the session alive. However, it does not explicitly state when to prefer this over alternatives, nor does it mention when not to use it, leaving the guidance mainly implied.

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