Api iam password reset create

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

Annotations already declare non-readOnly, openWorld, non-idempotent, non-destructive, so the safety profile is partially covered. The description adds nothing beyond that — no mention that a reset likely triggers an outbound email to the target user, whether the call requires authentication, or what state it mutates.

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?

It is short, but only because it is empty of content — a bare identifier is under-specification, not conciseness, and gives the agent nothing to front-load.

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 security-sensitive, open-world, non-idempotent auth operation with no output schema, the description supplies no explanation of effect, side effects, or required context. An agent cannot safely decide whether to invoke it.

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 tool takes zero parameters and the schema is closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 applies.

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 is literally the tool's identifier restated ('api_iam_password_reset_create'), with no verb/resource articulation an agent could not already derive from the name. It does not distinguish this from siblings like iam_password_reset_confirm_create or iam_change_password_create.

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?

There is no guidance at all on when to call this versus the many adjacent IAM tools (password_reset_confirm, change_password, set_password), nor any prerequisite such as needing an existing user or unauthenticated access.

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