aws_logs_tail

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

Annotations already indicate read-only, non-destructive operation. The description adds behavioral context: it runs once (not streaming), wraps CLI for consistent time parsing, and advises optimization for long windows. No contradiction with annotations.

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 only 5 sentences, front-loading the purpose, and each sentence adds value: core function, CLI wrapping, output format, non-streaming behavior, and optimization advice. 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?

Given no output schema, the description only vaguely mentions 'Returns recent events as JSON.' It lacks specifics about output structure, error handling, or API limits (e.g., CloudWatch Logs pagination). Adequate but could be more 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 description coverage is 100%, so the baseline is 3. The description does not add new parameter-level information beyond what the schema already provides, but it reinforces the use of `filterPattern` and `since` for narrowing.

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 tails CloudWatch Logs for a log group, wraps the 'aws logs tail' CLI, and returns recent events as JSON. It distinguishes itself from a streaming tail and from sibling tools by focusing on a single fetch operation.

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 provides explicit guidance on usage: run once to fetch the window, call again with a later `since` for continuous tailing, and narrow long windows via `filterPattern` or lower `since`. It lacks explicit when-not-to-use comparisons with siblings, but the context makes the use case clear.

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