diagnostic_signatures__logs__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds resource scope ('logs belonging to a diagnostic signature') but does not disclose additional behaviors such as pagination details, ordering, or rate limits, which are only implied by the schema.

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 a single sentence with an endpoint reference, conveying the essential purpose without unnecessary words. It is front-loaded and every element is useful.

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 simple read-only list operation with strong annotations and a fully described schema, the description is complete. It lacks explicit mention of pagination or return format, but the schema parameters (limit, next_url) cover pagination, and no output schema is present to explain return values.

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% for all three parameters, with clear descriptions for 'id', 'limit', and 'next_url'. The tool description itself adds no parameter-specific meaning, so the schema carries the full burden. 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 clearly states 'List the logs belonging to a diagnostic signature', specifying the verb and resource. It distinguishes this tool from siblings like 'builds__diagnostic_signatures__list' by focusing on logs of a signature. The endpoint reference reinforces the purpose.

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 usage context (when you have a diagnostic signature and need its logs) but does not explicitly state when to use it versus alternatives or mention any prerequisites. The parameter description for 'id' hints at a matching list call, but that is beyond the tool description itself.

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