lattice_database_action

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

Without annotations, the description warns that 'remove' destroys the container and data survival depends on volumes or snapshots. This adds critical safety context. However, it doesn't disclose other behaviors like idempotency or error states for start/stop/restart.

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 with critical warning about data destruction. No wasted words; all information is front-loaded and earns its place.

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 tool's simple actions and no output schema, the description covers the main behavior and the destructive case. However, it could mention expected return values or error behavior for completeness.

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 descriptions already cover both parameters (id and action) with clear labels. The tool description does not add extra parameter-level detail beyond the schema, so baseline 3 applies per schema coverage >80%.

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 verb (start, stop, restart, remove) and resource (database instance's container), and distinguishes it from sibling tools like lattice_stop_container by targeting database containers specifically.

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 implies usage for database container lifecycle, but does not explicitly compare with sibling tools (e.g., lattice_stop_container) or provide when-not-to-use guidance. Context allows inference but lacks explicit direction.

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