list_diagnostics_databases

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds no extra behavioral context, such as permissions, response format, or filtering behavior. It is consistent with annotations but offers no new disclosure.

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 very short with no filler words, and it includes the endpoint for clarity. The brevity is acceptable, but the wording could be more precise; otherwise it is appropriately concise.

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 tool has no parameters and an output schema, the description carries a relatively low burden. Yet it does not explain what 'Database Diagnostics' means, how it differs from list_diagnostics or list_diagnostics_logs, or any usage context. The phrase 'Download' could mislead an agent into expecting a file download rather than a list.

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 in the input schema, so the baseline is 4. The description need not explain parameters; it is a parameterless call and adds nothing here.

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 'Download Database Diagnostics' identifies a verb (Download) and a resource (Database Diagnostics), but it is vague about the exact action—it doesn't explicitly say 'list' or indicate the returned object is a list of databases. It also does not differentiate itself from sibling tools like list_diagnostics or list_diagnostics_logs.

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 given on when to use this tool versus other diagnostics-related tools. The description does not mention alternatives, conditions, or context for selection.

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