add_org_member

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

Discloses key behaviors: new wallet provisioning as human principal, default role, and owner requirement. No annotations provided, so description carries full burden. Covers main behavioral aspects but lacks error handling or idempotency info.

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?

Three concise sentences, front-loaded with action and resource. Every sentence adds distinct value. No redundant or excessive text.

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, prerequisite, parameter nuances, and behavioral traits. No output schema or annotations, but description is fairly complete for a creation tool. Could mention error cases or existing membership handling, but not critical.

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% (baseline 3). Description adds meaning: wallet as EVM address/named wallet with provisioning effect; role defaults to developer with owner requirement. Adds value beyond 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 action: 'Add a member to an org BY WALLET'. Mentions endpoint and distinguishes from email invite flow, differentiating from sibling tools like invite_auth_user.

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?

Specifies prerequisite (active owner membership) and role default. Mentions alternative flow (email invite) as separate, but doesn't explicitly state when not to use or list other alternatives.

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