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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavioral context: OUT_OF_RANGE means the range ends before the oldest kept log, default ordering is newest-first within the page, and the payload is flagged 'Untrusted' (a prompt-injection caution). Return format and rate/volume behavior remain unstated, so not a 5.

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?

Every clause carries information and the differentiating statement is front-loaded early. The telegraphic fragments ('OUT_OF_RANGE = ...', 'Untrusted.') are efficient, though the one-word 'Untrusted.' is slightly cryptic without further framing.

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 an 8-parameter, no-output-schema read tool with a nested filter object, the description covers return content, error semantics, ordering defaults and data-trust posture, which is most of what an agent needs. Pagination and limit truncation behavior live in the schema, so the remaining gap is minor.

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 coverage is 75%, so the schema already carries most parameter meaning (limit caps, stream enum, end_time default, page_token usage). The description adds only the default start/order framing ('since oldest_kept_time', 'by default the newest, oldest first'), which is largely redundant with from_start and start_time descriptions. Baseline 3 is appropriate.

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 names the concrete resource ('the containers' stdout and stderr lines') and explicitly routes latency questions elsewhere ('not which path is slow: that is QueryHttpTraffic'), so an agent can separate it from its closest sibling. The verb is only implied by the tool name rather than stated, which keeps it just short of a 5.

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?

It gives a clear use case (diagnosing what a request failed with) and names the alternative tool for the adjacent question (which path is slow -> QueryHttpTraffic). It stops short of explicit when-not conditions or prerequisites, so no 5.

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