mortgage_start_login

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-read-only, non-idempotent action. The description adds that it starts a login flow but does not detail side effects like opening a browser or whether it returns a status. No contradiction with annotations; the additional context is limited.

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?

Three concise sentences, front-loaded with the purpose, followed by usage guidance and a safety note. Every sentence adds essential information with no redundancy.

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?

The description covers purpose, usage prerequisites, and a key constraint. It does not explain the return value or what happens after the login flow starts, but the schema's parameter descriptions and the tool's context (initiating the selected login route) make it reasonably complete for 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 description does not elaborate on parameters, but the schema provides descriptions for 2 of 3 params, and the route enum (onepassword/manual) is self-explanatory. The description adds no additional parameter meaning, but the schema sufficiently covers the required inputs.

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 ('Start') and resource ('user-selected headed UWM login flow'), clearly indicating the tool's function. It distinguishes from sibling data-retrieval tools by referencing the login flow and the prerequisite from mortgage_connection_status.

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?

Explicitly states the precondition: 'Use only after presenting the choices from mortgage_connection_status.' Also provides a clear exclusion: 'Never request credentials or MFA in chat.' This gives the agent concrete guidance on when and how to use the tool.

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