query_logs

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavioral context: logs are searched within a time window and returned newest first. It does not contradict annotations and provides concrete ordering/scoping behavior beyond the safe-read label.

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 concise—three short sentences—and front-loaded with the primary purpose. The second sentence offers actionable tips, and the third states ordering. No filler or redundant restatement of the tool name.

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 the output schema exists and annotations cover read-only safety, the description provides sufficient context for a log-search tool. It explains the core use case, useful filtering strategies, and result ordering. The sibling list makes it clear where this tool fits. Missing details like limit defaults are already present in the schema.

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 burden. It explains level (filter to ERROR), contains (grep substring), and time window (since_minutes) with concrete examples like trace ID and timeout. It does not explicitly mention limit, but the schema's default/min/max make that self-evident.

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: 'Search a service's logs within a time window.' This clearly distinguishes it from sibling tools like list_services, get_metrics, and get_deploys, which target other resource types. The time-window scope and 'returns newest first' detail further clarify the tool's role.

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 gives practical guidance: using level="ERROR" to skip noise and contains to grep for substrings like trace IDs or error codes. It implies this tool should be used for log investigation, which contrasts with the metrics/deploy/incident siblings, though it does not explicitly name an alternative or exclusion.

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