ad_reset_user_password

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

No annotations are provided, so the description carries the full burden, and it delivers only the DESTRUCTIVE tag plus a vague 'com seguranca' claim. It says nothing about required permissions, whether the old password must be known, what dry_run or confirmation_token gate, or that must_change_at_next_logon defaults to true and will force a reset at next logon.

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?

It is a single front-loaded line with no filler, which is structurally fine, but the brevity comes from omission rather than discipline. The space saved was needed for parameter and safety context.

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?

This is a destructive credential mutation with six parameters, no annotations, and no schema descriptions; the description does not compensate. An output schema exists, so return values needn't be explained, but the invocation-time behavior and parameter meaning gaps are substantial.

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% across six parameters, and the description mentions none of them. Critical semantics for dry_run, confirmation_token, correlation_id, and the default-true must_change_at_next_logon are left entirely undocumented.

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?

States a specific verb+resource ('Redefinir senha de usuario') and prefixes it with the [Users] domain and [DESTRUCTIVE] severity tags, so the agent knows exactly what operation this is. It does not differentiate from siblings such as ad_update_user or ad_unlock_user, which also touch user credentials, so it stops short of 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 indication of when to use this versus ad_update_user, ad_unlock_user, or ad_get_password_expiring_users, and no prerequisites are stated. The [DESTRUCTIVE] tag implies caution but gives no exclusions or conditions for invocation.

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