mysql_change_password

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

Annotations supply the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's marginal burden is lower. However, the description adds nothing behavioral: it does not warn that the previous password becomes invalid immediately, note any authentication/permission requirement, or clarify the scope of the change. It only restates the argument list.

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?

Front-loaded with the action, followed by a compact Args block; every line earns its place. The loss is minor (the Args list is a schema echo), but there is no wasted prose.

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 tool mutates credentials, has a full output schema and annotations, and 3 parameters at 0% schema coverage. The description documents the parameters but omits any usage context or behavioral consequence of the change, leaving the definition only minimally complete for a security-relevant mutation.

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 0%, so the description must carry the semantics, and it does document all three parameters in one line each, including the default for 'access' (localhost). It loses a point for not clarifying what 'suffix' refers to (a DB name suffix vs. full name) or the expected password format.

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 states a specific verb+resource ('Сменить пароль к базе MySQL'), so the agent knows exactly what operation occurs. It does not distinguish itself from siblings like mysql_add_access, mysql_drop_access, or the parallel ftp_change_password/mail_change_password tools, which is the only thing keeping it from a 5.

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?

There is no guidance on when to use this tool versus alternatives such as mysql_add_access or mysql_delete, nor any prerequisites (e.g. that the DB/suffix must already exist). The agent must infer the trigger condition entirely from the name.

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