wait_for_account_creation

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses exponential backoff with jitter, terminal states, the connection-scoped session behavior, the user_id field in the terminal body, and the equivalence of new-user vs existing-user flows.

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 dense but every sentence adds value: core behavior, retry policy, lifecycle semantics, and usage context are all covered without unnecessary filler. The 'Agent usage' section front-loads the most actionable guidance.

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 having no output schema, the description gives an agent everything needed to call and interpret the tool correctly: how to start, what terminal states mean, what the user_id field indicates, and how to handle a pending timeout. It is complete for a polling tool of this complexity.

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% and both parameters already have solid descriptions. The tool description adds operational context by saying the id comes from create_account and that a pending result should be retried with the same id, which slightly exceeds the baseline.

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 names a specific verb and resource — 'Poll an account-bootstrap session' — and clearly ties it to 'after create_account with the returned session id.' This distinguishes it from the many sibling wait_* tools by identifying the exact flow it serves.

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?

It gives explicit when-to-use guidance: 'Call this after create_account with the returned session id' and explains what to do on a 'pending' result. It does not explicitly state when not to use it or name alternatives like wait_for_login or wait_for_session, so it stops short of a 5.

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