list_user_password_methods

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

No annotations are provided, so the description carries the full burden. It merely restates the tool's name and does not disclose behavioral details such as read-only status, required permissions, pagination, or response characteristics.

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 clear sentence with no redundancy or unnecessary detail, achieving maximum conciseness.

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 relatively simple and the output schema likely covers return format, but the description omits guidance on how 'password authentication methods' differ from related concepts (e.g., MFA status) and provides no edge-case context. It is functional but lacks surrounding information to fully distinguish tool usage.

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?

The input schema has one parameter, user_id, with no description (0% coverage). The description implies that user_id identifies the user whose methods are listed, which adds some meaning, but it does not specify the ID format or any additional semantics.

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 uses a specific verb ('List') and resource ('a user's password authentication methods'), making the tool's purpose immediately clear. It also distinguishes from the sibling tool 'get_user_password_method' (singular) by using the plural 'methods'.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_user_password_method' or 'get_user_mfa_status'. It lacks any mention of exclusions or contextual scenarios.

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