list_hostgroups

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention that the tool returns paginated results (implied by parameter), auth requirements, or that it is a read-only operation. The 'List' verb implies reading, but this is minimal.

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 succinct, with the purpose in the first sentence and an optimization note in a separate line. It avoids unnecessary words, though it could include more details without sacrificing conciseness.

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?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description minimally covers the purpose but omits crucial details like pagination behavior, default return size, and output format. The context optimization hint is helpful but insufficient for complete understanding.

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 has one parameter 'per_page' with 0% description coverage, and the tool description does not explain its meaning. The schema's title 'Per Page' provides a weak hint, but the agent receives no clarification on how to use pagination or the effect of the parameter.

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 all hostgroups in Foreman,' specifying the verb and resource. While it distinguishes from sibling tools by focusing on hostgroups, it does not explicitly differentiate from other list_ tools that are similarly named.

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 includes a context optimization hint recommending search when there are 50+ hostgroups, providing practical usage guidance. However, it does not specify when to use this tool versus alternatives like search_hosts_by_hostgroup, which operates on hosts rather than hostgroups.

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