Api iam login create

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

Annotations declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, but the description adds nothing about what the call does, what credentials the body must contain, whether it establishes a session, or what side effects occur. For a non-idempotent, open-world login operation this is a critical omission.

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 not verbose, but that is because it contains essentially no content at all — a bare identifier is under-specification rather than conciseness. There is no front-loaded purpose statement or structure to speak of.

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 a non-idempotent, open-world login endpoint with an undocumented free-form body and no output schema, the description should explain the credential payload and resulting session behavior. It says nothing, leaving the definition unusable for correct 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?

Schema coverage is 0% and the single 'body' parameter is an unconstrained anyOf object with a null default. The description supplies zero information about required fields (e.g. username/password or token payload), so the agent has no way to construct a valid call from either source.

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 the literal string "api_iam_login_create", which merely restates the tool name and title. It conveys no verb-plus-resource meaning beyond the identifier itself, and gives no hint that this is an authentication/login endpoint distinct from the many iam siblings such as iam_session_token_create or iam_auth_tokens_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 when-to-use guidance, no mention of alternatives among the crowded iam_* family, and no prerequisite or sequencing information. An agent cannot infer from the text alone whether this authenticates a user, issues a session, or is a step in a flow.

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