list-hosts

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

With no annotations, the description must convey behavior but only states it 'lists hosts'. It does not disclose that the operation is read-only, the output format (handled by schema but not summarized), or any limitations like pagination. This is insufficient for an agent to understand 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?

The description is a single concise sentence with no extraneous words. It efficiently conveys the primary action, though it could benefit from slight expansion to cover key details without becoming verbose.

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?

The tool has three optional parameters and no output schema, yet the description offers no context on default behavior (e.g., default inventory path, default format), return structure, or how group filtering changes results. An agent would need to infer from parameter names alone, which is incomplete.

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 description coverage is 100% (all three parameters have descriptions), so baseline is 3. The tool description adds no additional meaning beyond the schema, e.g., it does not explain how group filtering works or the impact of format choices.

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 verb 'list' and resource 'hosts in inventory', making the tool's purpose immediately obvious. It distinctly differs from sibling tools like 'inventory-status' or 'compare-inventory-state' by focusing on listing 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'inventory-status', 'list-environments'). The description does not mention prerequisites, typical use cases, or exclusions, leaving an AI agent without decision context.

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