cloudwatch_get_log_events

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

With no annotations, the description carries full burden. It discloses the dual behavior (raw events vs ranked summary), the performance hint of avoiding huge pulls, and the summary_only option. However, it does not mention read-only nature, cost, or rate limits. The time window (hours_back) is implied in 'last N hours'.

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, front-loaded with purpose. The second sentence is dense but packs the key modal distinction. Could be split for readability, but overall efficient without waste.

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 9 parameters, no output schema, and no annotations, the description covers the main use cases but lacks detail on the return format (e.g., structure of raw events) and does not mention the max_events cap or the filter_pattern auto-quoting behavior. Adequate but not fully 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?

With 100% schema coverage, baseline is 3. The description adds value by explaining that group_by produces a server-side ranked summary with default top_n=20, and that summary_only returns just the count. It also hints at the performance benefit. This goes beyond the schema's descriptions.

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 tool fetches recent events from a CloudWatch log group, with optional filtering and an aggregation mode via group_by. It distinguishes itself from siblings like cloudwatch_top_ips (specific field) and cloudwatch_insights (analytics) by highlighting the raw vs ranked summary duality.

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 implies usage for fetching recent log events and offers a summary mode to avoid large pulls, but it does not explicitly state when to use this tool over alternatives like cloudwatch_insights or cloudwatch_top_ips. No when-not or explicit comparison to sibling tools.

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