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

No annotations are present, so the description carries the full burden. It does disclose a key behavioral trait: 'Returns new password once,' which is valuable because the new password cannot be retrieved later. However, it does not mention whether the old password is immediately invalidated, if there are impacts on existing sessions, or any authentication requirements.

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 two sentences long, front-loaded with the action, and contains no filler. Every word contributes to understanding the tool's purpose and key return behavior.

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 one-parameter tool, the description covers the core action and the return value. However, it lacks usage guidance and explicit side-effect warnings (e.g., irreversible password change, inability to see the password again), which would be expected given the lack of annotations.

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 fully covers the address parameter with its description, and the schema description coverage is 100%. The tool description adds minimal context by clarifying that the password being reset is the SMTP password, but it does not add format, syntax, or usage details beyond the schema.

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-resource pair: 'Reset the SMTP password for an email account.' This clearly distinguishes it from sibling tools like create_email_account or set_personal_email_credentials, which have different functions.

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 is provided on when to use this tool versus alternatives. For instance, there is no mention of when reset_account_password is preferred over set_personal_email_credentials, and no caveats or prerequisites are given.

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