kia_forget_session

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

The description discloses that the tool makes no network call and only forgets locally, beyond the idempotentHint annotation. It also explains the preview behavior without confirm:true.

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?

The description is concise, containing only essential information in a clear structure. It covers purpose, use cases, behavior, and parameter effect without extraneous content.

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's simplicity (one optional boolean parameter, no output schema), the description is fully complete. It covers all necessary context: local action, no network call, recovery use case, and confirm behavior.

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 single parameter 'confirm' is well-described in the schema, but the description adds important context about its effect: without it, nothing is deleted and a preview is returned. This adds value beyond the schema.

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 the tool discards the locally stored Kia session to force re-authentication. It distinguishes from sibling tools like kia_session_status and kia_start_login by specifying it is for forgetting the session.

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 explicitly states when to use it: as a recovery path when the stored token no longer works due to revocation, password change, or device move. It also notes the only alternative is manual file deletion, providing clear guidance.

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