ad_responder

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

With no annotations, the description carries full burden but fails to disclose key behaviors: whether the process runs in the background, required privileges, potential system impact, or how to stop it. The term 'poisoner' hints at network manipulation but provides no concrete operational detail.

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 a single, front-loaded sentence, but it is under-specified. While concise, it omits essential information, making it inadequate rather than appropriately sized for a tool with multiple parameters.

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 the tool's complexity (network poisoning, 3 parameters), the description is grossly incomplete. It lacks any mention of return values, runtime behavior, or parameter usage, and with no output schema, the agent has no way to understand what to expect.

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?

The schema has 3 parameters with 0% description coverage, and the description does not mention any of them. No meaning is added for 'analyze', 'interface', or 'additional_args', leaving the agent without guidance on how to use these parameters.

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 action ('Start') and the resource ('Responder LLMNR/NBT-NS poisoner'), identifying the tool's unique function among siblings. However, it does not elaborate on what poisoning entails or why one would use it, slightly limiting clarity for unfamiliar agents.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or conditions. The description only states the action, leaving the agent to infer that it should be used when LLMNR/NBT-NS poisoning is needed.

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