query_logs

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds useful behavioral detail: an empty filter matches all logs, results are returned newest first, and freshness controls the lookback window. This complements the annotations without contradicting them.

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 compact and well-structured, leading with the core purpose before listing parameter details. Every line provides useful guidance without repeating schema defaults unnecessarily.

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 query tool with no required parameters, it covers invocation essentials: filter syntax, time window, result ordering, and environment selection. The return shape is not described, but that is a minor gap given the tool name and read-only annotations.

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 full responsibility for parameter meaning. It thoroughly explains all four parameters with examples, defaults, and edge-case behavior such as empty filter and default environment.

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 queries Cloud Logging using an advanced-filter expression. It identifies the resource and action specifically, though it does not explicitly differentiate itself from sibling tools like get_recent_errors or query_metric.

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 this is the tool for flexible Cloud Logging queries by explaining filter, freshness, limit, and environment. It does not explicitly state when to prefer sibling tools like get_recent_errors or list_error_groups for error-focused queries.

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