host_info

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Get information' with no details about the returned data, error behavior, authentication requirements, or side effects. The description adds no context beyond the obvious read operation, leaving the agent without important operational expectations.

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, efficient sentence with zero wasted words. It is appropriately sized for a simple tool.

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 tool with one parameter and no output schema, the description is minimal but functional. However, it does not hint at what 'information' includes (e.g., IP addresses, status), which would help set expectations. Given the low complexity, a score of 3 reflects an adequate but not enriched description.

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 fully describes the single parameter 'host' as 'The hostname to get information for' (100% coverage). The description provides no additional meaning beyond this, so the baseline score of 3 applies—schema does the heavy lifting.

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 ('Get') and the resource ('a nameserver host'), making the tool's basic purpose evident. However, 'information' is generic and doesn't specify what details are returned, nor does it distinguish this tool from the sibling host_list, which also retrieves host data.

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 intended use is implied: call this to get details for a specific host, given the required 'host' parameter. However, there is no explicit mention of when to use this instead of host_list or any other alternative, nor any exclusions or prerequisites.

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