lattice_list_database_snapshots

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns size and creation time but does not mention pagination, ordering, or permissions. For a simple read-only list, this is adequate but not detailed.

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 concise sentences with no wasted words. The verb 'List' leads the description, and the second sentence adds valuable usage context.

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 simple list tool with one parameter and no output schema, the description is nearly complete: it states what the tool does, what it returns, and when to use it. It lacks mention of pagination, but that may not be necessary for snapshots.

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% for the one parameter 'id', which is described as 'Database instance ID'. The description does not add additional meaning beyond the schema; it simply restates the parameter's role in context.

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 lists snapshots for a database instance, specifying that it returns size and creation time. It distinguishes from sibling snapshot tools (lattice_create_database_snapshot, lattice_restore_database_snapshot, lattice_delete_database_snapshot) by focusing on listing.

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 to check this before deleting or restoring an instance, giving clear context for when to use the tool. This distinguishes it from sibling tools that perform actions on snapshots.

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