kia_start_login

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

Discloses that without confirm:true no network call is made, that failed logins count and can cause permanent reCAPTCHA lockout, and that credentials must be pre-configured. Annotations only provide readOnlyHint and idempotentHint, which are insufficient; description fills the gap.

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?

Five sentences, each adding unique value: purpose, precondition, dry-run behavior, warning, and required state. No redundancy. Front-loaded with the most critical information.

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 complexity (MFA bootstrap, permanent lockout) and lack of output schema, the description covers purpose, preconditions, dry-run mode, return values (otpKey, xid), and critical warnings. Adequately prepares the agent for safe 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?

Only parameter 'confirm' is well-described in schema (must be true to proceed). Description adds context about dry-run preview and network call behavior, reinforcing the schema. Schema coverage is 100%, so baseline 3; description adds meaningful usage context.

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?

Clearly states it's Step 1 of a one-time MFA bootstrap, identifies the verb ('start login') and resource ('Kia MFA bootstrap'), and distinguishes from sibling tools like kia_send_otp and kia_verify_otp.

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 specifies preconditions: only needed when kia_session_status shows hasSession:false. Explains dry-run behavior with confirm:false and warns against repeated failures due to permanent lockout risk.

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