neurover_node_cancel

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond that: it says nothing about what happens to partial results, whether the call is idempotent, or what occurs if no generation is running.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity edges into under-specification rather than being genuinely tight.

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 operation with no output schema, zero schema description coverage, and no annotation detail about side effects, one short sentence is not enough. An agent lacks what it needs to know about preconditions and post-call state.

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% across three parameters (workflowId, nodeId, account), so the description must carry the explanatory burden. It only loosely implies node scope via 'плитка' and never explains the required workflowId or the optional account parameter, leaving most parameter meaning undocumented.

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 names a specific verb ('Отменить' / cancel) and a specific resource (a generation currently running in a tile/node), so the operation is identifiable. It does not, however, distinguish this from lookalike siblings such as neurover_cleanup_cancel or neurover_reset_context, and 'плитка' (tile) never explicitly maps to the required nodeId.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives. An agent must infer from the word 'идущую' (in progress) that this only applies to a currently executing generation, and must guess what to do if the node is idle.

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