local_ydb_set_root_password

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

The description reveals key behaviors: it performs ALTER USER, syncs host auth config and password file, and warns about password complexity rejection. It does not contradict any annotations (destructiveHint=false is consistent since password rotation is not data-destructive). The confirm parameter's plan-only behavior is also noted.

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 two sentences that efficiently cover the core action, syncing behavior, and a notable caveat (password complexity). No redundant or unnecessary information is present.

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?

Given the tool has 4 parameters (with good schema descriptions) and no output schema, the description adequately covers the main functionality, preconditions, and side effects. It could mention that profile and configPath are optional, but that is already in the schema. Overall, a complete and helpful description.

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 coverage is 100% with parameter descriptions. The tool description adds value by explaining the plan-only behavior for confirm and reiterating the non-empty requirement for password, which is already enforced but reinforced. This goes beyond the schema's basic descriptions.

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 clearly states the tool rotates the runtime root password using ALTER USER and syncs related config files. Among siblings like local_ydb_prepare_auth_config and local_ydb_write_dynamic_auth_config, this tool is uniquely focused on the root password, making its purpose distinct.

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 provides some usage context, such as the possibility of password rejection due to complexity rules and the requirement of a non-empty password. However, it does not explicitly compare this tool to siblings or specify when to use it over alternative auth-related tools.

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