database.snapshots

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action ('List') and resource ('database snapshots'), implying a read-only operation but not explicitly stating it. It does not disclose pagination behavior, required authentication, or any side effects.

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 short sentence, which is concise, but it is under-specified for the complexity of the tool. It earns its place by stating the core purpose, but fails to provide necessary details.

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 presence of three parameters (including a required one), no schema descriptions, no output schema, and no annotations, the description is highly incomplete. It does not explain return values, pagination, session requirements, or the scope of snapshots listed.

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 description coverage is 0%, and the tool description adds no information about the three parameters (limit, offset, session_id). The agent must infer their meaning solely from parameter names, which is insufficient for a tool with pagination and a required session identifier.

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 snapshots' uses a clear verb+resource pattern. It distinguishes from sibling tools like database.create_bndb, database.save_auto_snapshot, and database.info, which have different actions. However, it leaves minor ambiguity about whether it lists snapshots for the current database or all 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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or context for choosing this over other database-related tools.

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