seerr_create_user_settings_password

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

Annotations already declare readOnlyHint=false. The description adds 'WRITE: this modifies your Seerr instance,' which reinforces the mutability but provides no additional behavioral context such as side effects, permission requirements, or specific changes beyond password. No contradiction with annotations.

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, front-loaded with the primary action and a brief warning. It contains no redundant verbiage.

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?

The tool is under-specified for a password update. It fails to explain what the body should contain, whether the current password is needed, or any permission constraints. The presence of an output schema doesn't compensate for input ambiguity.

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%, and the description only says 'Update password for a user,' giving no details about the body parameter structure, required fields, or password format. The body is an open object, leaving the agent without sufficient information to construct a valid request.

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 states 'Update password for a user' which clearly identifies the action and target. This distinguishes it from sibling tools like seerr_get_user_settings_password (retrieval) and other user settings tools. Despite the tool name containing 'create', the description clarifies it's an update.

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 vs alternatives such as seerr_update_user or seerr_get_user_settings_password. No mention of prerequisites like admin privileges or authentication, nor any exclusions.

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