htb_hosts_show

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

With no annotations, the description carries the full burden and does disclose the main return structure and the effect of full=true. It does not explicitly state that the tool is read-only, nor does it cover permissions, side effects, or pagination behavior.

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 short, front-loaded with the main return shape, and then explains the two parameters in context. Every sentence adds useful information without repetition.

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?

There is no output schema and no annotations, so the description should ideally explain the returned structure more fully. It identifies top-level entries/groups and the full=true inclusion behavior, but it does not describe the fields within those structures or other relevant output details.

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?

Schema coverage is 100%, so baseline is 3, but the description adds useful meaning: `patterns` narrows the selected entries exactly as htb_hosts_select does, and full=true includes unmanaged/system entries such as localhost. It clarifies that pattern filtering applies to entries rather than groups.

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 states a specific resource and result shape: a structured overview of managed hosts, with both flat entries and grouped-by-box groups. It is clear what the tool returns, but it does not explicitly distinguish its purpose from siblings such as htb_hosts_select or htb_hosts_list_backups.

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?

Usage is implied through 'overview', the `patterns` narrowing behavior, and the `full=true` option for unmanaged/system entries. However, it does not explicitly say when to use this tool instead of htb_hosts_select or other sibling tools.

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