cloudwatch_list_log_groups

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists log groups and shows stored bytes and retention, but does not mention that it is a read-only operation, potential costs, pagination behavior, or any other traits. The absence of such details leaves significant behavioral unknowns.

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 extremely concise, consisting of two sentences with no wasted words. It front-loads the core purpose and then provides an additional detail about what information is displayed. Every sentence serves a purpose.

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 simple nature of the tool (list with optional filter) and the absence of an output schema, the description adequately covers the key aspects: what it does and what information it returns. It does not mention pagination or that multiple groups may be listed, but for a list operation this is generally acceptable. The description is sufficient for understanding the tool's basic functionality.

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?

Schema coverage is 100%, so the baseline is 3. The description adds minimal semantic value beyond the schema: it reinforces that filtering is optional and that the region defaults to the boto3 default. However, the schema already provides this information ('Filter to log groups whose name starts with this prefix', 'defaults to the boto3 default region when empty'). The description does not significantly enrich understanding.

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 the verb 'List' and the resource 'AWS CloudWatch log groups', and specifies optional filtering by name prefix along with additional details shown (stored bytes and retention). This effectively distinguishes it from sibling tools like cloudwatch_get_log_events (which retrieves log events) and cloudwatch_top_ips (IP statistics).

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 indicates the tool is for listing log groups with an optional prefix filter, which implies its primary use case. However, it lacks explicit guidance on when to use it versus alternatives (e.g., cloudwatch_insights for querying log data), and does not mention when not to use it or any prerequisites. The usage context is implied but not fully clarified.

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