kia_verify_otp

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

The description reveals that the remember-me token is stored locally and not returned, sessions refresh silently, and MFA becomes permanent – all beyond the annotations. No contradiction with annotations.

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?

Two sentences: first gives purpose, second explains behavior and effect. No wasted words, efficiently communicates 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 tool is part of a multi-step MFA process, the description covers prerequisites, effect on state, and future behavior. No output schema needed as the description explains return value (none). Fully complete.

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 100% with good descriptions. The tool description adds context about sourcing otpKey and xid from kia_start_login but does not significantly supplement the schema. Baseline 3 is appropriate.

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 clearly states this is 'Step 3 of the Kia MFA bootstrap' with the verb 'exchange' and resources 'passcode' and 'session'. It distinguishes from sibling tools by indicating its position in a sequence and referencing kia_start_login.

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?

The description says the resulting token is stored locally and MFA is never needed again, implying when to use it (after login, before other tools). It does not explicitly state when not to use, but the context is clear enough.

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