list_database_backups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds 'across the account' to clarify scope. This provides additional context but does not elaborate on pagination, performance, or other behavioral traits. With annotations covering the safety profile, the description adds marginal value.

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, clear sentence. It contains no fluff and is appropriately front-loaded with the purpose and scope.

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 it is a simple list tool with no parameters, no output schema, and comprehensive annotations, the description sufficiently covers what the tool does and its scope. No additional information is necessary.

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 and schema coverage is 100%. The baseline for no parameters is 4. The description does not add parameter information, but none is needed.

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 'List database backup configurations' clearly states the verb and resource. It distinguishes from sibling tools like list_databases, get_database_backup, and run_database_backup by specifying it lists configurations (settings) rather than actual backups or 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?

The description provides context that it lists configurations across the entire account, indicating usage scope. However, it lacks explicit guidance on when not to use it or alternatives, such as using get_database_backup for a specific backup.

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