link_wallet_to_organization

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a failure condition ('Fails if the wallet is already linked elsewhere') but omits whether the operation is reversible, idempotent, or requires specific permissions. No side effects or safety details are mentioned.

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 two sentences, front-loads the core action, and includes both the outcome and a failure condition. Every sentence adds value without redundancy or fluff.

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?

Given no output schema and no annotations, the description provides only minimal context: purpose and one failure case. It lacks details on success output, error handling beyond the one condition, or operational context like idempotency. For a simple two-parameter tool, this is adequate but not thorough.

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?

The input schema already provides clear descriptions for both parameters (org_id from create_email_organization, wallet as 0x... address). The description does not add new parameter-level meaning beyond this, which is acceptable given 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?

The description clearly states the verb 'Link', the resource 'wallet to an existing email organization', and provides specific context about enabling hybrid Stripe + x402 access. It also mentions a failure condition, making the purpose unambiguous and distinct from siblings like create_email_organization.

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?

The description implies the organization must exist (via create_email_organization) but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites beyond that. Siblings include create_org and other wallet-related tools, but no differentiation is given.

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