derivation_abort

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

No annotations are provided, so the description carries the full burden. It does disclose a key behavioral trait—that the session is saved and resumable—but lacks detail on side effects like whether the derivation state is cleared or marked as aborted, or any permissions required.

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 extremely concise, consisting of two short sentences plus a generic returns line. Every sentence serves a purpose: stating the action, the persistence behavior, and a return placeholder. No waste or fluff.

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 tool with an output schema, the description covers the core purpose and the key persistence fact, but it fails to explain the session_id parameter or its default behavior. This omission means the agent may not know how to correctly invoke the tool, making it incomplete despite the output schema.

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 input schema has one parameter (session_id) with a default value but no description, and the tool description also omits any explanation of how this parameter is used or what the default represents. With 0% schema coverage, the agent receives no guidance on passing this parameter.

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 states the action as '放棄當前推導' (abandon current derivation), with a specific verb and resource. It is distinct from related siblings like 'resume', 'complete', and 'rollback'.

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 explicitly notes that the session remains on disk and can be resumed later with derivation_resume, giving clear usage context and an explicit alternative tool. This helps the agent decide when to use this tool versus resume.

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