tdarr_admin_reset_password

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

The description states 'reset' which implies a destructive change, but no annotations are provided. The description does not disclose behavioral traits such as whether the password is immediately changed, if confirmation is required, or any rate limiting. For a sensitive admin operation, more transparency is needed.

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 sentence with no unnecessary words. It is front-loaded and concise. However, it could be slightly more structured to include behavioral notes without adding length.

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's simplicity (one parameter, no output schema), the description is nearly sufficient. However, lack of behavioral details and usage guidance leaves gaps for a sensitive admin action, making it minimally adequate.

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?

Input schema is fully covered with description for the single parameter ('Username to reset'). The tool description does not add any additional meaning beyond the schema, but schema coverage is 100%, so baseline score of 3 is appropriate.

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?

Description clearly states the action ('reset a user password') and the resource ('a user'). It is specific enough, but does not explicitly distinguish from 'tdarr_auth_reset_password' which may be a self-service reset. Without that differentiation, an agent might confuse the two.

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 tool versus siblings like 'tdarr_auth_reset_password' or what prerequisites are needed (e.g., admin privileges). The absence of context about appropriate scenarios or exclusions makes it harder for an agent to select this tool correctly.

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