link_wallet_to_organization

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

Since no annotations are provided, the description carries full burden. It discloses a failure condition and the effect (enabling hybrid access), but does not mention authorization requirements, whether the operation is idempotent, or any other side effects. For a mutation tool, this is adequate but not comprehensive.

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 covering purpose and a key behavioral note (failure condition). No redundant information, front-loaded with the main action.

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 the tool's simplicity (2 required parameters, no output schema), the description covers the essential purpose and a notable failure case. It does not describe the success return value, but that is generally acceptable for a straightforward mutation.

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?

Input schema provides full descriptions for both parameters (org_id and wallet), making the schema coverage 100%. The description adds context about the overall purpose but does not add new parameter-specific meanings beyond 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?

Description clearly states the action (link wallet to organization), the resource (existing email organization), and the outcome (enabling hybrid Stripe + x402 access). It distinguishes from siblings by specifying the linkage operation, which no other sibling tool explicitly performs.

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?

Description provides clear context that the organization must already exist (implied by 'existing email organization'), and mentions a failure condition (wallet already linked elsewhere). However, it does not explicitly state when NOT to use this tool or suggest alternative tools.

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