reset_database_passwordGives the user a new password, returned here; the old one stops working within seconds, so update the application first or right after. Scope: databases.write.
| Name | Required | Description | Default |
|---|---|---|---|
| database | Yes | Database id, as returned by list_databases or create_database. | |
| username | Yes | Lowercase letters, digits and _, starting with a letter or _. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description communicates high-impact behavioral traits (instant password invalidation) that go beyond standard operational status. Coupled with the annotations (`destructiveHint: true`), it paints a complete picture of the tool's risk and immediate impact.
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?
The two sentences are extremely efficient. The first sentence states the output/action, and the second addresses the critical operational consequence, maximizing informational density.
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?
The description covers all necessary aspects: what it does, its immediate consequence, and how the resulting new password should be handled. Given the high-risk nature (destructiveHint: true), this level of transparency is required and provided.
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 description coverage is 100%, providing a baseline of 3. The description adds valuable semantic context by confirming the parameters are an ID (`database`) and a user identifier (`username`). No further compensation is strictly necessary here.
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 title and description clearly state the action (resetting a password) and the resource (database). It is distinguishable from sibling tools like `get_database_credentials` because it performs an active change rather than a retrieval.
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 includes a critical, real-world behavioral guideline: the old password stops working within seconds. It explicitly instructs the user on the necessary sequence of operations (update application first or right after), preventing state mismatches.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.