Create database snapshot

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

Annotations already indicate readOnlyHint=false (write) and destructiveHint=false (non-destructive), which the description partially confirms by describing creation. The word 'manual' adds some context about snapshot type, but no additional behavioral traits (e.g., performance impact, permissions, concurrency) are disclosed.

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?

A single sentence of 11 words, front-loaded with the action verb and resource, no wasted words. The description is appropriately sized for a straightforward creation tool.

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 no output schema and a simple mutation, the description is adequate but lacks information about return values (e.g., snapshot ID), naming rules, or idempotency, which would help the agent fully understand the tool's behavior.

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?

Input schema has 100% description coverage for all parameters (name, database, description). The description does not add meaning beyond the schema, such as clarifying 'manual' or naming constraints; baseline of 3 is appropriate when schema carries the burden.

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 action ('create') and resource ('manual snapshot for a database cluster'), using a specific verb and resource that distinguishes from sibling tools like list, get, delete snapshots and create database restore.

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 no guidance on when to use this tool versus alternatives (e.g., automated snapshots), no prerequisites (e.g., database cluster must exist), and no exclusions. The agent is left without context to decide between this and other create tools.

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