growsurf_create_account

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

Beyond the annotations (destructive, non-idempotent), the description explains key lock behavior, 403 errors with specific error code, 7-day auto-deletion, key rotation on sign-in, and email domain restrictions. These are behavioral traits not declared in annotations and are essential for the agent to manage 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?

The description is long but every sentence imparts a distinct behavioral detail, from verification to deletion policies. It front-loads the core purpose and then methodically lists constraints and next steps, so the length feels justified rather than padded.

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 multi-step account creation with verification, error handling, and alternative tools, the description covers the workflow, error codes, retry logic, and cleanup policy. It also notes the output returns `apiKey`, making it self-contained for an agent to execute 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 coverage is 0%, so the description must compensate, but it only mentions that email must not be personal or disposable, adding one constraint. It provides no guidance on `company`, `lastName`, or `firstName`, leaving their semantics to the schema field names alone.

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?

States a specific verb and resource: 'Create a brand-new GrowSurf account and return an API key.' It distinguishes itself from siblings by noting it is the only tool that does not require `GROWSURF_API_KEY`, making its purpose unique and clear.

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?

Provides a clear workflow: create the account, verify email, retry on error, and explicitly names the alternative `growsurf_resend_team_owner_verification_email` for lost emails. Also mentions prerequisites such as team verification for certain actions and the 7-day deletion timeline.

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