tdarr_auth_reset_password

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

No annotations provided, so the description carries full burden. It mentions 'current user' but does not disclose side effects (e.g., whether session is invalidated after password change, rate limits, or security implications). The description is too minimal for a sensitive mutation.

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, which is efficient, but it omits critical information. True conciseness would provide necessary context without fluff; here it is under-specified.

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 simple two-parameter tool with no output schema and no annotations, the description should explain the authentication context, success/failure indications, and any side effects. It fails to do so, leaving the agent uninformed.

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 basic descriptions ('New password', 'Current password'), but the description adds no further meaning (e.g., password complexity rules, length limits, or verification behavior). Baseline 3 is not met because the description fails to compensate for the minimal schema 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 'Reset current user password' clearly states the action and resource, distinguishing it from the sibling 'tdarr_admin_reset_password' which likely resets another user's password. However, it could be more precise, e.g., 'Reset the password for the currently authenticated user.'

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 the sibling 'tdarr_admin_reset_password' or other authentication tools. The agent receives no context about prerequisites (e.g., user must be logged in) or alternatives.

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