user_password_auth_delete

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

No annotations provided, so the description carries the full burden. It reveals nothing about irreversibility, auth requirements, or side-effects of disabling password authentication for a user, which is a security-sensitive operation.

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?

Very short, but not front-loaded with useful information; it's essentially a raw API endpoint dump (method, path, tag, spec) which is more noise than signal for an agent selecting/calling the tool.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't state consequences, reversibility, or any behavioral context needed for safe invocation.

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%, so both parameters are fully documented in the schema itself. The description adds no parameter meaning beyond the schema, but baseline 3 is appropriate when schema does the heavy lifting.

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 action (DELETE) on a specific resource (/user/password-auth), and the Russian gloss 'Отключить вход по паролю' (disable password login) clarifies it. However, it's largely a restatement of the name using HTTP method + path, with no differentiation from sibling user_password_auth_post or other auth tools.

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?

No guidance on when to use this vs alternatives like user_passkey_delete or user_otp_delete, nor prerequisites. The confirm parameter hints at a preview mechanism, but the description doesn't elaborate on when/how to use it.

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