hosts_clear

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

Discloses that system entries are never touched and that only the managed section is cleared. Mentions return value (count). With no annotations, this covers key behavioral aspects, though missing details on permissions or side effects.

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?

Extremely concise with four short sentences, each serving a purpose: action, clarification, use case, and return value. Effectively front-loaded with the main action.

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?

Fully covers the tool's purpose, behavior, return value, and example. Given the tool's simplicity and no output schema, the description is complete and informative.

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 schema coverage is trivially 100%. The description adds value by explaining the scope and effect of the operation beyond the empty schema, meeting the baseline of 4 and exceeding with contextual detail.

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?

Description explicitly states the tool removes all managed /etc/hosts entries, clarifying it only affects the Kali-MCP managed section. It differentiates from siblings like hosts_remove by being a bulk clear operation.

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 a clear use case ('switching to a completely new target'). Does not explicitly mention when not to use or alternatives, but the context is sufficient for an agent to infer.

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