get_recent_errors

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context: only severity ERROR or higher is returned, results are ordered newest first, and service matching applies to both resource.labels.service_name and logName. 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 one-line purpose statement is followed by a compact, alphabetized Args list covering all four parameters with no filler. Every sentence adds useful information.

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?

For a read-only log retrieval tool with no required parameters and no output schema, the description covers invocation and behavior well. It lacks an explicit description of the returned entry fields or pagination, but the parameter semantics plus annotations make calling the tool correctly feasible.

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 0%, so the description carries the full burden, and it delivers. Every parameter is explained: service matching semantics, hours-back with default, maximum limit with ordering, and environment selection with default behavior.

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 a specific verb and resource: 'Return recent log entries at severity ERROR or higher.' It differentiates by severity and recency, which separates it from broader tools like query_logs, though it does not explicitly name or contrast any siblings.

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 when to use this tool—when recent error-level logs are needed—and explains optional narrowing by service and environment. However, it gives no explicit guidance about when to prefer a sibling tool such as query_logs or list_error_groups, nor any exclusions.

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