list_diagnostic_logs

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

Annotations are missing, so the description bears full responsibility. It states the tool returns 'individual log entries' and works for a 'performance issue', but does not disclose read-only nature, pagination behavior beyond the limit parameter, or any authorization requirements.

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 two sentences with no unnecessary words, front-loading the core action and prerequisite information efficiently.

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 simple two-parameter schema and no output schema, the description is mostly complete. It covers purpose, prerequisite, and core behavior, but lacks details on output format or edge cases like empty results.

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 100%, so baseline is 3. The description adds context for signatureId by explaining how to obtain it, but does not enrich limit beyond the schema's description.

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 it lists diagnostic logs for a specific diagnostic signature, with a clear verb ('list') and resource ('diagnostic logs'), and distinguishes from the sibling tool list_diagnostic_signatures by requiring a signature ID.

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 explicitly instructs to use list_diagnostic_signatures first to get the required signature ID, providing clear ordering and prerequisite guidance.

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