jan3_login_start

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

Describes the process: crafts signed L-BTC tx, posts to endpoint, server emails OTP. Discloses it's a paid step. Lacks info on failure modes or side effects, but otherwise transparent.

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, front-loaded with purpose and usage, no unnecessary words.

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?

Covers the step's purpose, prerequisite, and next step. No output schema, but the process is clear enough for an agent to use.

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 100% with descriptions; description adds context like email receives OTP, password decrypts wallet, wallet_name funds payment.

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 it's a fallback login method (paid captchaless) and explains the first step of crafting a signed L-BTC tx. It distinguishes from the free email-OTP 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 'use only when the free jan3_login email-OTP flow isn't available for the account' and directs to call jan3_login_complete next.

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