get_log_errors

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

No annotations provided, but description discloses read-only behavior (no modification), that raw logs are never returned, and optional filtering. Lacks details on permissions or rate limits but is sufficiently transparent for a simple read tool.

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?

Three concise sentences: first on what it returns, second on what it doesn't, third on usage. Front-loaded with key information, no fluff.

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?

Covers output, limitations, usage, and filtering. Lacks output schema or return format details, but given single optional parameter and simple purpose, it is adequately 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?

Schema has 100% coverage for the single parameter with description. The tool description adds that the filter uses a 'name substring', enhancing meaning beyond the schema's 'Filter to a specific log group name (optional)'.

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?

Clearly states it returns error pattern summaries from CloudWatch log groups, specifying output (counts and frequencies) and what it excludes (raw log messages). Distinguishes from siblings by focusing on log error patterns.

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?

Explicitly says to call when investigating errors or identifying log groups with no retention policy. Provides clear use case but lacks direct comparison to siblings or when-not-to-use guidance.

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