lattice_get_database_credentials

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

With no annotations, the description highlights that this tool is unsecured and un-audited, contrasting with the replacement. It does not detail other behaviors like authentication requirements or rate limits, but the deprecation context mitigates the need.

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?

Single sentence with deprecation warning and replacement instruction. Every word is necessary and front-loaded.

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 deprecation, the description suffices for basic understanding but does not specify the return format of the credentials, which a user may still need if they invoke the tool despite the warning.

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% with a single well-described parameter. The description adds no extra meaning to the parameter beyond what the schema already provides.

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 'returns root credentials from a plain GET' and distinguishes itself from the audited and scoped replacement lattice_reveal_database_credentials.

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 using the replacement tool instead, providing clear guidance against using this deprecated tool. However, it does not elaborate on when one might still need to use this tool.

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