aiworkhub_dispatcher_stop

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 idempotent behavior via 'if any' and the consequence ('no cross-repository read or delivery can happen afterward'), but says nothing about error modes or whether stopping an unstarted dispatcher errors versus no-ops.

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?

Two short sentences, no filler; the action and its scope are front-loaded before the rationale. Every clause earns its place.

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?

An output schema exists, so return values need not be described, and the description covers action, scope, and effect. Only minor operational detail (idempotence edge cases, error behavior) is absent.

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?

Zero parameters, so the baseline is 4; there is no argument surface for the description to clarify, and it correctly implies a no-argument invocation.

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 specific verb pair ('Stop and unregister') and a specific resource ('the active repository's callback dispatcher'), explicitly scoping to the active repo. It is clearly distinguishable from sibling aiworkhub_dispatcher_ensure_started and other dispatcher tools.

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?

It names the triggering contexts ('workspace/repository switch and extension deactivation'), which tells the agent when this is invoked. It does not explicitly name the opposite tool (dispatcher_ensure_started) or state when not to call it, so it stops short of a full routing statement.

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