callback_start

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

Describes that it runs HTTP and DNS servers, and returns status with port and IP info. However, it does not mention that listeners run in background or need to be stopped explicitly, nor any resource implications. With no annotations, a bit more detail on lifecycle would improve transparency.

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?

Very concise and front-loaded. First sentence captures core function, then expands with context, params, return, and example. No filler or repetition.

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?

Covers purpose, usage, parameters, return value, and example. With an output schema present, return info is sufficient. Lacks mention of background execution or need for cleanup, but overall complete for starting a listener.

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?

Despite zero schema description coverage, the description fully explains each parameter with defaults and usage context (e.g., bind_ip hint to use tun0). Examples further clarify invocation. Schema only provides names and defaults, so description adds all necessary meaning.

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 explicitly states it starts HTTP and DNS listeners to capture out-of-band callbacks, clearly distinguishing from sibling callback tools like callback_check or callback_stop. It also differentiates from webhook.site by specifying when to use this tool (no internet access).

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?

Provides explicit guidance to use instead of webhook.site when target has no internet access. Does not explicitly mention when not to use, but context implies alternatives. Could add more about prerequisites or state management.

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