list_work_groups

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'List all Athena work groups' and does not mention pagination behavior, result ordering, response contents, or whether any permissions are required. The pagination arguments are present but their behavioral implications are not described.

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 short and front-loaded with the core purpose, followed by a compact Args section. Every sentence earns its place, and there is no redundant or filler content.

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 simple list operation with two optional parameters and an output schema, the definition is nearly complete: purpose and parameters are covered. It loses one point because it lacks explicit guidance on when to use this vs. get_work_group and does not describe pagination behavior beyond the token parameter.

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 has 0% coverage, but the description's Args section explains max_results as 'Maximum number of results to return' and next_token as 'Token for pagination,' adding meaning the schema itself lacks. This is minimal but sufficient for these two straightforward optional parameters.

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 states a specific verb ('List') and resource ('all Athena work groups'), making the tool's purpose immediately clear. It also distinguishes itself from sibling tools like get_work_group, which targets a single workgroup, and list_databases/list_tables, which target different Athena resources.

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?

Usage context is implied rather than explicit: 'List all Athena work groups' suggests this is for enumerating workgroups, and the sibling get_work_group implies the alternative for fetching a single workgroup. However, the description does not explicitly state when to choose this over related tools or mention any prerequisites or exclusions.

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