List Permission Groups

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

Annotations already declare readOnlyHint=true, making the safe read-only nature clear. The description adds that it lists 'all' groups but offers no further behavioral details (e.g., pagination, ordering, or response format). The bar is lower due to annotations, but the description provides minimal additional context.

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?

Two sentences, no wasted words. Every sentence serves a purpose: stating the action and linking to a common use case. Highly efficient.

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 tool is simple with no parameters and good annotations, the description omits details about the return value, such as the fields included in the response (e.g., id and name). Without an output schema, the description should explain what the agent can expect, which it does not. This gap reduces completeness.

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?

There are zero parameters, and the schema coverage is 100%. According to guidelines, a tool with no parameters receives a baseline of 4. The description does not add parameter info because there are none.

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 Guide permission groups' with a specific verb and resource, and adds the secondary purpose of finding the permission_group_id for creating articles. This distinguishes it from other list tools like list_categories or list_sections.

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?

It explicitly tells the agent to use this tool to obtain a permission_group_id when creating articles, providing a direct use case. However, it does not specify when not to use it or mention alternatives, though for a simple list tool this is not critical.

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