bootstrap_start

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

Discloses that it sends an OTP email, the token TTL (10 min), and that human interaction is required. Annotations indicate non-readonly, non-destructive, non-idempotent, which aligns with the description. No contradictions.

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?

Well-structured with clear sections: core action, when to use, tips, note. Front-loaded with the most critical information. Every sentence adds value without redundancy.

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?

Despite no output schema, the description explains the return values (bootstrap_token, account_id). Covers all important behavioral aspects: OTP email, time limit, human intervention, blocked domains. Complete for a single-parameter tool.

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 already covers the email parameter with format and pattern. Description adds that OTP is sent to this address, which is implicit. With 100% schema coverage, 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?

Clearly states it is step 1 of a 2-step flow, emails an OTP, and returns bootstrap_token plus account_id. The sibling bootstrap_verify is explicitly mentioned, distinguishing their roles.

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 when to use: 'Kicking off a new seller account.' Provides actionable tips: ask for email, tell human to check inbox, call bootstrap_verify promptly, and disposable domains blocked.

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