lattice_update_database_instance

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

No annotations provided, so the description carries full burden. It states it's a mutation and partial update, but doesn't disclose potential side effects, error conditions, or permission requirements. The schema mentions a port conflict scenario, but the tool description omits this.

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 that is front-loaded with the main purpose and includes a key behavioral note about partial updates. No redundant or irrelevant information.

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?

Despite having 13 parameters and no output schema, the description provides minimal context. It doesn't explain return values, error handling, or common use cases, leaving the agent to rely heavily on the schema and inference.

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?

With 54% schema coverage, the description adds no parameter-level detail beyond the general action. It does not explain the meaning or implications of fields like status, health_status, or schedules, leaving interpretation to 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 action ('Update') and the resource ('database instance's configuration'). It distinguishes from siblings by specifying 'database instance' among many update tools for different entities.

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?

It indicates partial updates ('Only the fields you pass are changed'), but lacks explicit guidance on when to use this tool versus alternatives like create or delete, or any prerequisites.

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