clear_get_groups

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

No annotations are provided, so the description must convey behavioral traits. It states it returns a list, which implies a read-only operation, but does not disclose whether it has side effects, authorization requirements, or performance implications. For a simple list retrieval, this is adequate but not thorough.

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, clear sentence that conveys exactly what the tool does. No extraneous words or unnecessary detail. It is perfectly concise and front-loaded.

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 no parameters and a straightforward purpose, the description is mostly complete. It could benefit from defining what 'clear groups' are, but the sibling tools provide some context. The lack of output schema is not critical for such a simple list retrieval.

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 zero parameters, so schema description coverage is 100%. The description adds no parameter information, but according to the rubric, 0 parameters yield a baseline of 4. The description does not need to compensate further.

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 name 'clear_get_groups' and description 'Get a list of all configured clear groups' use a specific verb 'Get' and resource 'clear groups'. It clearly distinguishes from siblings like 'clear_get_group' (singular) and 'clear_trigger_group' (which triggers rather than lists).

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 provides no guidance on when to use this tool versus alternatives. For example, when to use 'clear_get_groups' vs 'clear_get_group' vs 'clear_trigger_group' is not mentioned. There is no context about prerequisites or use cases.

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