start_account_signup

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

With no annotations provided, the description carries the full burden. It discloses that signup is email-verified, that only the person can finish, and that no credential is returned. This is meaningful behavioral context that goes beyond the schema and helps set expectations.

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 with zero fluff. The main action is front-loaded, and the follow-up sentence adds critical constraints. Every word contributes value.

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 single-parameter tool with an output schema present, the description covers the essential purpose, precondition, and a key aspect of the return (no credential). It could mention error conditions or duplicate email handling, but those are likely handled by the output schema. Overall, it is adequately complete for an agent to invoke it correctly.

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. It indirectly explains the email parameter by mentioning 'email-verified signup' and 'sending an email', implying the email is the verification target. However, it does not explicitly describe the parameter's format or constraints, leaving partial gap.

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 ('Start email-verified signup') and the resource involved (email). It distinguishes itself from siblings like start_agent_pairing by focusing on account signup, and it conveys a clear purpose that is not a tautology.

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 specifies the precondition 'after the person approves sending an email', giving clear context for when to invoke it. It does not explicitly name alternatives, but the sibling set contains no direct signup alternative, so the context is sufficient for a reasonable agent.

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