get_log_group_info

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

No annotations provided, so the description carries full burden. It states 'get detailed information' but does not explicitly declare read-only behavior, side effects, permissions needed, or rate limits. While 'get' implies no mutation, the description lacks explicit behavioral disclosure.

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 a single sentence with no redundancy or fluff. It efficiently conveys the tool's purpose and includes one useful behavioral note about the environment variable.

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?

Without an output schema, the description partially covers return values by mentioning 'retention settings and storage', but it lacks details on other common fields like creation time, stored bytes, or metric filters. For a simple tool, this is adequate but not comprehensive.

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% with a description for the parameter, and the description adds value by noting that the logGroup parameter defaults to the CLOUDWATCH_LOG_GROUP environment variable. This provides context beyond the schema alone.

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 uses a specific verb 'get' and identifies the resource as 'CloudWatch log group', mentioning specific details like 'retention settings and storage'. It clearly distinguishes from sibling tools like list_log_groups, which lists groups, and query_logs_insights, which searches logs.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., list_log_groups for listing, search_logs for searching). The description only implies that you need a specific log group name and mentions an environment variable fallback, but does not provide context for decision-making.

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