kia_send_otp

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

Discloses that the passcode expires in ~2 minutes and reports expiresAt, and that it has no confirm gate. Annotations already indicate non-readOnly; description adds useful context without contradiction.

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 brief sentences covering purpose, dependency, channel guidance, and expiry. No wasted words, front-loaded with core purpose.

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?

Adequately covers prerequisite, channel selection, and expiry. Lacks explicit description of response format (e.g., success/expiresAt), but sufficient for a simple send tool with no output schema.

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%. Description adds context on where otpKey and xid come from (kia_start_login) and that notifyType should be determined by asking the user, which goes beyond schema descriptions.

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 2 of MFA bootstrap, delivers a one-time passcode via SMS or email. Distinguishes from siblings by specifying dependency on kia_start_login and its place in the flow.

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 says it requires otpKey and xid from kia_start_login, advises asking user for channel, and notes expiration. Does not explicitly state when not to use it, but provides clear context on prerequisites.

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