cloudwatch_search_logs

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

No annotations are provided, so the description carries full burden. It does not mention whether the operation is read-only, potential costs, error handling, or behavior on large queries. The description only explains parameters without behavioral context.

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?

Extremely concise: one sentence stating purpose followed by parameter list with examples. No wasted words, front-loaded with the main action.

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 an output schema exists (though not shown), the description adequately covers inputs. It includes time range and limit, which are critical for query tools. Could mention pagination or result format, but overall sufficient for basic usage.

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 0% schema description coverage, the description compensates by listing all 4 parameters with examples (e.g., 'log_group: 로그 그룹 이름 (예: /ecs/logispot-api)') and default values. Adds meaning beyond the bare schema.

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 executes CloudWatch Logs Insights queries, providing specific verb ('실행') and resource ('CloudWatch Logs Insights 쿼리'). It distinguishes from sibling tools like cloudwatch_list_log_groups (list log groups) and cloudwatch_get_alarms (get alarms) by focusing on query-based log search.

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 guidance on when to use this tool versus alternatives (e.g., when to use cloudwatch_get_metric vs this). The description does not mention scenarios, prerequisites, or boundaries.

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