list_permission_groups

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

With no annotations provided, the description carries the behavioral burden. It conveys a read-only scoping operation ('List ... for an account'), but does not disclose pagination, response shape, permission requirements, or whether the output includes all groups or only those directly assigned. This is adequate for a simple list operation but not richer.

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?

A single sentence with no wasted words; the verb, resource, and scope are front-loaded. Every word earns its place.

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?

The tool has only one required parameter, and the schema fully documents it. However, there is no output schema and the description does not describe return values or pagination, which would be needed for an agent to fully interpret results. For a simple list with one well-documented parameter, the description is minimally viable but not complete.

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 schema description for account_id is complete ('The account ID') and coverage is 100%, so the baseline is 3. The tool description adds no parameter meaning beyond reaffirming 'for an account,' which mirrors the schema rather than adding new semantic detail.

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 a specific action ('List'), a specific resource ('IAM permission groups'), and a scope ('for an account'). It differentiates from siblings like get_permission_group (singular) and list_token_permission_groups (token-specific) by using 'IAM' and 'list', though it does not explicitly name those alternatives.

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?

There is no guidance on when to use this tool versus get_permission_group, list_token_permission_groups, or list_account_roles. The description does not state when this tool is appropriate or when a sibling should be preferred, leaving the agent to infer usage from the name alone.

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