list_diagnostics_logs

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

The description discloses that this is a download and shows the HTTP method GET, which reinforces the read-only, idempotent, non-destructive nature already declared in annotations. However, it adds minimal extra behavioral context (e.g., output format, authentication needs, size) beyond what annotations convey. With annotations present, a 3 is appropriate.

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 extremely concise: one line for the action and one line for the endpoint. It is front-loaded with the verb and resource, and contains no wasteful content.

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 zero parameters, an output schema present, and annotations covering the safety profile, the description is nearly sufficient for invoking the tool. The only gap is not explaining what the log bundle contains or expected response, but the output schema likely covers that.

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?

There are zero parameters, so the schema coverage is effectively 100%. Per the baseline for 0 params, the description does not need to add parameter detail, and it correctly does not.

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 ('Download') and resource ('Log Bundle'), and includes the exact endpoint 'GET /diagnostics/logs'. This makes the action clear, though it does not explicitly differentiate from sibling tools like list_diagnostics or list_diagnostics_databases.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it is the way to obtain a log bundle, nor does it exclude other diagnostic-related tools. The context for selection among siblings is entirely absent.

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