list_hosts

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

No annotations are provided, and the description only repeats pagination details from the schema. It does not disclose any behavioral traits, such as performance implications, authorization requirements, or whether the result is sorted. The mention of a nonexistent 'settings' parameter further harms transparency.

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 relatively short but includes an unnecessary and incorrect 'settings' line. The structure is clear with labeled sections but could be more focused.

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?

While the output schema exists, the description lacks context about the scope of 'all managed hosts', any filtering, or how it differs from similar tools. With no annotations, the description does not sufficiently compensate for missing behavioral or contextual information.

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 description explains 'limit' and 'offset' for pagination, adding meaning beyond the raw schema. However, it also lists a 'settings' argument that does not exist in the input schema, which misleads the agent about available parameters.

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 'List all managed hosts/consoles,' clearly indicating a list operation. However, it incorrectly mentions a 'settings' parameter that is absent from the input schema, causing confusion.

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 on when to use this tool versus alternatives like 'get_host' or 'search_across_sites'. No discussion of prerequisites or limitations.

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