pmg_when_groups_list

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

Declares READ-ONLY status upfront, which is critical given the absence of annotations. Describes return format (list of group dicts with id/name/comment). Lacks details on pagination or error handling, but adequate for a list tool.

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?

Three concise sentences: purpose/config, return format, and alternative use cases. No redundancy, front-loaded with essential info.

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 (one optional param, output schema present), the description covers purpose, usage, return, and distinguishes siblings comprehensively. No gaps observed.

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?

Input schema covers 100% of the single parameter with a detailed description. The description adds no extra semantic value beyond the schema, which is sufficient for this tool.

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 specifies 'list all PMG RuleDB 'when' object groups' with a clear verb and resource. It distinguishes from siblings by naming alternative tools for 'who' and 'what' groups and for retrieving a single group's config.

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?

Explicitly states the tool's purpose (list all when groups) and when to use alternatives (pmg_who_groups_list, pmg_what_groups_list, pmg_when_group_get). It also mentions a prerequisite config (PROXIMO_PMG_*).

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