create_email_organization

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

Discloses important behaviors: sends a verification email (side effect) and idempotency (duplicate emails return existing org). Since no annotations exist, description carries the full burden and does well.

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 no redundant information. First sentence states purpose and key qualifiers; second adds behavioral details. Highly concise and front-loaded.

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 purpose, qualifiers, side effects, and idempotency. For a simple one-parameter tool with no output schema, this is largely complete. Could mention return value but not essential.

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 the parameter description already includes the Stripe-only qualifier; the tool description adds no additional parameter-specific meaning beyond what's in the schema.

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 'Create an email-based organization' with specific qualifiers 'Stripe-only, no wallet required', distinguishing it from sibling tool 'create_org' which likely handles wallet-based organizations.

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 indicates when to use (email-based, Stripe-only) and hints at alternatives (no wallet). Does not provide explicit when-not-to-use or alternative names, but the context is clear.

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