list_dead_hosts

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 'List all 404 dead hosts' with no details on whether the operation is read-only, what permissions are required, or if there are side effects. The phrase 'all' implies no filtering but does not clarify if results are paginated or limited.

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 extremely concise at 6 words, with no redundant information. It is front-loaded with the core purpose, making it immediately clear what the tool does. Every word earns its place.

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 simplicity (no parameters, no output schema, no annotations), the description is reasonably complete. It clearly states the output is a list of all 404 dead hosts. However, it lacks details on whether the list includes status codes or how the 'dead' status is determined, which could be inferred from context.

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 input schema has 0 parameters with 100% schema description coverage. The description correctly implies no parameters are needed by stating 'List all' without any filtering conditions. It adds no additional meaning beyond the schema, but for a parameterless tool, this is sufficient.

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 'List all 404 dead hosts' with a specific verb ('list') and resource ('dead hosts'). It distinguishes itself from sibling tools like create_dead_host, delete_dead_host, and list_proxy_hosts by specifying the exact subset of hosts.

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 description does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of scenarios where list_proxy_hosts or other list tools would be more appropriate. No when-not or exclusion criteria are given.

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