create_database_backup

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

Annotations already declare destructiveHint=true and openWorldHint=true. The description adds context about scheduling vs. immediate backup but does not elaborate on the destructive aspect (e.g., whether creating a configuration overwrites existing ones). No contradiction with annotations, but the description could provide more behavioral detail.

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?

Two sentences with no wasted words. The purpose is front-loaded, and the alternative tool is mentioned immediately. Perfectly 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 5 parameters with full schema coverage and no output schema, the description covers prerequisites, scheduling vs. immediate usage, and parameter semantics. It lacks return value details, but for a creation tool this is acceptable. Overall, it provides sufficient context for selecting and invoking the tool.

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 covers 100% of parameters, so baseline is 3. The description adds value by clarifying that 'backup_configuration' must be a pre-existing destination (a subtlety not in schema). This contextual hint improves usability beyond the schema alone.

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 creates a SCHEDULED database backup configuration, differentiating it from 'run_database_backup' which triggers an immediate backup. The verb 'create' and specific resource 'database backup configuration' leave no ambiguity.

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?

Explicitly states the prerequisite of a pre-existing backup destination and directs to 'run_database_backup' for immediate execution. This provides clear when-to-use and when-not-to-use guidance, including an alternative sibling.

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