get_recent_errors

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results are aggregated by error class rather than returned raw — but says nothing about the default time window (1 hour), the default cap (20), or whether aggregation can hide individual events.

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?

A single front-loaded sentence with no filler, which is structurally sound. It is arguably over-terse given four parameters and a grouping behavior worth explaining, but nothing in it is wasted.

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?

The output schema exists, so return values need not be explained. However, with 0 required parameters and three of four parameters undocumented in both schema and description, plus an undefined 'recent', an agent lacks enough to call this confidently beyond the default configuration.

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 only 25% (only service_name is documented), and the description contributes nothing about limit, since, or account_ids. Notably, 'recent' in the description is ambiguous while the schema quietly defaults since to '1 HOUR AGO' — the description could have resolved that and did not.

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 states a specific verb and resource ('Show recent transaction errors') plus an aggregation mode ('grouped by error class'), which is more than a restatement of the name. It does not, however, differentiate itself from near-neighbors like summarize_log_errors or search_logs, so an agent must infer the distinction.

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?

There is no statement of when to use this tool versus the alternatives, and no prerequisites (e.g., that a time window is assumed). The word 'recent' is the only usage signal, and it is left undefined.

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