redis_change_password

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: it does not say whether Redis is restarted, whether existing connections are dropped, whether the change is reversible, or what permissions are required. It merely restates the tool name.

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 three-word phrase is front-loaded but is under-specification rather than genuine conciseness — there is no information to trim because almost none is given. It reads as a title repeated rather than a usable description.

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 mutating tool with no annotations, no output schema, and two undocumented required parameters, the description is wholly inadequate. An agent cannot determine the meaning of 'id', the effect on the running Redis instance, or whether prerequisites must be met before invoking.

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% for two required parameters. The description gives no clue that 'value' is the new password, and the numeric 'id' parameter is completely unexplained (which entity's password?). At most, the word 'password' weakly hints at 'value', leaving 'id' opaque.

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?

'Redis: Change password' names a specific verb (change) and resource (Redis password), and the 'Redis:' prefix separates it from the mysql_/postgresql_ siblings. It does not, however, distinguish it from nearby Redis tools such as redis_update_conf, so it stops short of full sibling differentiation.

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 indication of when this should be used versus redis_update_conf or the other password-change tools, no prerequisites (e.g. whether Redis must be running, whether the caller needs admin rights), and no exclusions. The description provides no usage guidance at all.

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