combell_mysql_users_set_password

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

Annotations already state readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description only confirms a mutation and adds no additional behavioral context, such as whether changing the password disconnects active sessions, requires privileges, or takes effect immediately. There is no contradiction with annotations.

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 description is a single front-loaded sentence with no filler, and every word carries meaning. It is concise, but the terseness contributes to under-specification in other dimensions, so it does not receive full marks.

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 tool with three required parameters, two of which are undocumented in both schema and description, and no output schema, this description is not complete enough for an agent to call it with full confidence. It lacks guidance on prerequisites, side effects, and how it relates to sibling MySQL user operations.

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 only 33%, and only 'password' is documented in the schema. The tool description does not explain 'user_name' or 'database_name' or their relationship, so it fails to compensate for the largely undocumented parameter set.

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 uses a specific verb, 'Change', and a clear resource, 'password of a MySQL database user'. This distinguishes it from siblings such as combell_mysql_users_create, combell_mysql_users_delete, and combell_mysql_users_set_status, and the 'MySQL' qualifier separates it from combell_mailboxes_set_password.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the tool name and sibling list that this applies to an existing MySQL user, and there is no mention of when set_password should be preferred over create or set_status.

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