Api iam change password create

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

The annotations already establish that this is a non-read-only, non-idempotent, non-destructive endpoint, but the description adds no behavioral context such as whether the current password is required, which sessions are affected, or what the response contains. For a security-sensitive account mutation, this leaves significant gaps in what the agent can anticipate.

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 front-loaded sentence with no filler or repetition. Its brevity is not the problem; the issue is under-specification, which is captured in other dimensions.

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 sensitive IAM context, an opaque body parameter, no output schema, and only minimal annotations, an agent needs much more information to invoke this safely and correctly. The description provides essentially none of the required context about authentication, payload shape, or effects.

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?

There is one parameter, "body", with 0% schema description coverage and no details in the description about its structure or required fields. The agent cannot determine whether the body should contain old/new passwords, user identifiers, or any other payload, so the description fails to compensate for the undocumented 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 restates the tool name/title almost verbatim: "An endpoint for changing password." It does not distinguish this tool from nearby IAM siblings such as set_password, password_reset, or password_reset_confirm, so an agent cannot tell from the description which password operation applies.

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 when-to-use guidance, no prerequisites, and no mention of alternatives like the password reset or set-password endpoints. The agent is left to infer usage entirely from the tool name and sibling list.

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