list-hosts

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

No annotations are provided, so the description must convey behavioral traits. The term 'List' implies a read-only, non-destructive operation, which is adequate. However, the description does not disclose any additional behaviors such as rate limits, pagination details, or response structure. It relies on the schema for parameter behavior, but the overall transparency is moderate.

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 consists of a single, well-structured sentence that immediately states the purpose and key capabilities. There is no redundancy or extraneous information, making it highly concise and efficient for an AI agent 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?

Despite having 8 parameters with good schema descriptions, the tool description lacks details about the output format, pagination limits, or typical use cases. It does not explain what fields are returned by default versus with includes. With no output schema, more context in the description would help an agent fully understand the tool's complete behavior.

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%, so the description adds minimal value beyond what the schema already provides. The description only mentions 'filtering, sorting, and metadata' which corresponds to existing parameters. No new constraints or clarifications are introduced, resulting in a baseline score.

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 infrastructure hosts with filtering, sorting, and metadata'. The verb 'list' and resource 'infrastructure hosts' are specific, and this tool is uniquely positioned among sibling list tools which target different resources (e.g., containers, processes, services).

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 mentions capabilities like filtering, sorting, and metadata, which implicitly guide usage. However, it does not explicitly state when to use this tool versus alternatives (e.g., get-host-totals), nor does it provide conditions or constraints. The resource name alone provides clear context, so a slight deduction is applied.

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