run_database_backup

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

The description lacks detail beyond the annotation destructiveHint: true. It does not explain what occurs during the backup run (e.g., whether it creates a file, impacts performance, or requires specific permissions). The description adds little behavioral context beyond the annotation.

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 concise sentences, each carrying essential information. The first states the action, and the second provides a practical pointer. No redundancy or filler.

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 tool that triggers an action (not a data query), the description is fairly complete given the simple parameter and annotations. It explains what the tool does and how to get the required ID. However, it could mention the result or side effects, but the destructive annotation partially compensates.

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% with a clear description for backup_id. The description adds a usage hint ('Use list_database_backups to find the backup id') but does not provide additional semantic meaning beyond the schema. Baseline score 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 the tool runs an existing database backup configuration immediately. The verb 'Run' and resource 'database backup configuration' are specific, and the phrase 'backup now' clarifies the action. It distinguishes from sibling tools like create_database_backup or list_database_backups.

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 advises using list_database_backups to find the backup ID, which helps the agent obtain the required parameter. However, it does not mention scenarios where this tool should not be used or provide alternative tools for similar purposes, though the context from sibling tools is implied.

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