Send client password reset

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

The description adds that this is a trigger action (sending an email) beyond the annotations (readOnlyHint=false, destructiveHint=false), which already indicate it is a non-read, non-destructive operation. It does not disclose potential side effects or required permissions, but with annotations present, the added context is reasonable.

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 single-sentence description is highly concise and front-loaded with the core action, containing only essential information. No wasted words.

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 simple two-parameter tool and existing annotations/schema, the description is adequate but does not mention return behavior or failure conditions, which could be important since there is no output schema. Still, it is sufficient for basic invocation.

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 already provides descriptions for both client_id and email, with 100% coverage. The description adds no additional parameter semantics, so it relies on the schema for this information, which is sufficient.

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 explicitly states the action ('Trigger'), the resource ('password-reset email'), and the target ('client'), clearly distinguishing it from sibling tools like resend_client_verification or update_client. It also notes 'admin-initiated' to clarify the context, making the purpose unambiguous.

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 phrase 'admin-initiated' provides clear context that this is for administrator-triggered password resets, not self-service. However, it does not explicitly mention alternatives or when not to use it, though the clear purpose implicitly differentiates it from similar email-sending tools.

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