pause_top_cook

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

With no annotations provided, the description carries the full behavioral burden. It does not state whether the pause is persistent or transient, whether it can be resumed, what state is affected, or what happens if no cook is running. For a state-mutating operation this is a significant gap.

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 purpose sentence is front-loaded and waste-free. The Args block, however, includes the boilerplate 'ctx: MCP context' which is noise rather than substance, slightly diluting an otherwise tight entry.

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?

No annotations, no output schema, and 0% parameter coverage leave the description as the only information source, yet it says nothing about return values, effect on queued work items, or how to resume cooking. Thin for a state-changing TOP operation.

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 schema documents nothing. The description adds one useful detail — node_path accepts either a TOP node or a TOPnet path — which is more than the schema gives, but it omits format examples (e.g. '/obj/geo1/mytop') or how a TOPnet path is resolved.

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?

States a concrete verb+resource: 'Pause cooking on a TOP network.' An agent can tell this is a state-changing operation on TOP cooking. However, it never distinguishes itself from the closely related siblings cook_top_node and cancel_top_cook, so the differentiation dimension is unmet.

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 guidance on when to pause versus cancel or resume cooking, and no mention of prerequisites such as an in-progress cook being required. The only hint of scope is the phrase 'TOP network', which implies TOPs but does not route the agent among the three TOP-cook siblings.

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