cancel_top_cook

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says nothing about whether a partially cooked result is preserved or discarded, whether the node must currently be cooking, what permissions or state are required, or how errors are reported. 'Cancel' vs 'pause' is the one behavioral distinction an agent most needs here, and it is only implied.

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?

One short sentence, front-loaded with the action and scoped to TOP networks, with no filler. It is efficient but borders on under-specified rather than merely concise.

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 state-changing tool with no annotations, no output schema, and an undocumented required parameter, the description is too thin. An agent cannot determine the node_path format, the preconditions for a successful cancel, or what happens to in-progress results.

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% for the single required parameter, node_path, so the schema contributes no meaning at all. The description does not explain whether node_path identifies the TOP node itself, the network, or a nested path, which is exactly the information missing from the schema.

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 states a specific verb and resource: 'Cancel active cooking on a TOP network.' An agent can tell this stops a running cook rather than starting one. It does not explicitly contrast itself with pause_top_cook, so the boundary between cancel and pause must be inferred from the names alone.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite pause_top_cook and get_cook_status existing as closely related actions. The agent is left to infer that this is for abandoning a cook entirely rather than suspending it.

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