thruk_list_hostgroups

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

The description provides minimal behavioral context: default columns returned. With no annotations provided, the description carries the full burden but omits side effects (none expected, but not stated), permissions, or output format details beyond default columns.

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 sentence with no unnecessary words. It is efficient, though it could include a bit more context 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?

For a tool with 5 parameters and no output schema, the description is incomplete. It lacks explanation of pagination (limit/offset), sorting, backends, and column selection customization. The minimal info leaves agents guessing.

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 adds information about default columns, which relates to output but not directly to parameters. Schema coverage is 60%, meaning some parameters lack descriptions, and the description does not compensate for those gaps.

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 action ('List host groups') and provides a specific detail about default columns, making the tool's purpose clear. However, it doesn't define what a host group is, but that is likely understood from context and the tool name.

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 given on when to use this tool versus alternatives like 'thruk_list_hosts' or 'thruk_list_servicegroups'. There is no mention of prerequisites or exclusions.

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