List databases

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

Highlights that passwords are redacted by default to avoid credential leaks, and mentions a parameter to reveal them. This adds safety-relevant behavior beyond the schema. However, it does not disclose other behaviors such as result format or pagination.

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 sentences, no extraneous words. Front-loads the main purpose and immediately explains the critical behavioral detail about password redaction.

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, the description covers the essential purpose and a key behavioral trait. However, it lacks detail on the output structure (what fields are returned) and does not mention any limits or pagination, leaving some gaps for an agent to fully understand the result.

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?

The parameter 'reveal_passwords' is described in the schema, and the tool description provides context about redaction policy, giving meaning to the parameter's use. This adds value beyond the schema's technical description.

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?

Description explicitly states 'List MySQL databases' and provides an alias 'get_databases'. It clearly identifies the resource (databases) and action (list), distinguishing it from sibling database tools like database_add or database_dump.

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 on when to use this tool versus alternatives. Does not specify appropriate contexts, prerequisites, or situations where other database tools would be preferred.

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