hosts_remove

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without explaining important traits: whether the operation is idempotent, what happens if the hostname is absent, whether it affects running processes, or if administrative privileges are required. This is a significant gap for a system-modifying tool.

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 with zero wasted words. It communicates the core purpose immediately and is appropriately sized for the tool's simplicity, making it easy to parse.

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?

For a mutation tool on a system file, the description is incomplete. It lacks details about side effects, prerequisites, or when to use this tool relative to its siblings. The sole parameter is not fully documented, and there is no output schema to clarify return values. This falls short of what is needed for safe and correct use.

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 0% description coverage, so the description must compensate. However, 'Remove hostname' simply repeats the parameter name 'hostname' without adding semantic detail such as format, exact match requirements, or whether IP addresses or aliases are also supported. The description provides no additional value over the schema's property definition.

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 'Remove hostname from /etc/hosts.' clearly states a specific action (remove) on a specific resource (hostname in /etc/hosts). It effectively distinguishes itself from siblings like hosts_add, hosts_list, and hosts_clear, which perform different operations.

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 such as hosts_add or hosts_clear. There is no mention of prerequisites, like checking current entries with hosts_list before removal, or scenarios where removal is appropriate. The description leaves usage to the agent's inference.

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