query_logs

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

Annotations already declare readOnly and idempotent, so the safety profile is covered. The description adds non-obvious behavior: results are ordered by timestamp descending and pagination is keyset-based via a 'nextCursor' token, which is genuinely useful beyond the annotations. It stops short of stating the concrete default/max limit values or any rate limits.

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?

Two tight sentences with zero filler; the ordering guarantee is front-loaded before the pagination note. Every clause carries information an agent needs.

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?

With no output schema the description usefully names the 'nextCursor' field, which is the one return detail an agent must know to page. For a 7-parameter filtered query tool this is nearly sufficient, though a note on default page size or the existence of service/trace/severity filters would close the gap.

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 every parameter including cursor, limit and the severity filter is already documented in the schema. The description only echoes the cursor contract already present, adding no new per-parameter semantics. Baseline 3 applies.

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?

States a specific verb and resource ('List log records') scoped to a UTC time window with an explicit ordering. The resource noun separates it from query_traces and query_metric_points, though it never names those siblings directly.

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?

Usage is implied: call this to enumerate log records in a window. It explains pagination mechanics but gives no explicit when-to-use versus query_traces or when to reach for list_log_services instead of filtering by service here.

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