login

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that the Cookie is persisted to the keychain and deliberately kept out of the model context, which is a significant security-relevant behavior. However, it does not explain what happens if the user is already logged in or whether the operation is destructive.

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 a single concise sentence that front-loads the action and purpose, then adds a key privacy detail. No word is wasted and all content is relevant.

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?

For a simple one-parameter login tool, the description covers the main purpose and an important security behavior. Yet it misses the meaning of the only parameter, force, and gives no guidance on when a forced re-login might be needed or how to verify auth state.

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 description coverage is 0%, so the description must compensate by explaining the force parameter, but it never mentions force at all. The parameter is entirely unexplained, leaving the agent unable to infer the effect or meaning of force.

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 a specific action (login to LeetCode China) and its key outcome (saving the Cookie to the system keychain). It is easily distinguished from siblings like auth_status, logout, and data-retrieval tools.

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 does not say when to use login versus auth_status or logout, nor does it mention prerequisites. It implies authentication is needed but gives no explicit usage context or alternatives.

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