callback_stop

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

The description discloses that both HTTP and DNS listeners are shut down, sockets are closed, and callbacks remain in memory. With no annotations provided, this fully covers behavioral traits.

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 concise with 5 sentences, front-loading the core purpose. It includes return information and an example with no wasted words.

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?

Given zero parameters and an output schema, the description adequately explains the tool's action, side effects, and return value. No further detail is necessary.

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?

No parameters exist, so the description needn't add parameter meaning. Baseline score of 4 applies as no parameter information is required.

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 tool stops the local callback catcher and cleans up listeners. It uses a specific verb (stop) and resource (callback catcher), distinguishing it from siblings like callback_start and callback_clear.

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 context of use is clear—after starting the callback catcher—but it doesn't explicitly mention when not to use it or directly contrast with callback_clear for memory cleanup, though it notes callbacks remain in memory.

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