Add Organization Member

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

Annotations provide substantial information: readOnlyHint=false indicates mutation, openWorldHint=true suggests flexible resource handling, idempotentHint=true implies safe retries, and destructiveHint=false indicates non-destructive. The description adds minimal behavioral context beyond this - it doesn't mention authentication requirements, rate limits, error conditions, or what happens on duplicate additions (though idempotency hints at safe retry). No contradiction with annotations exists.

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 a single, efficient sentence that states the core functionality without unnecessary words. It's front-loaded with the primary action and includes all essential elements (what, where, with what role). There's zero wasted verbiage or redundant information.

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 mutation tool with good annotation coverage but no output schema, the description is minimally adequate. It covers the basic operation but lacks important context about permissions needed, error responses, success criteria, or what the tool returns. The annotations help but don't fully compensate for the missing behavioral details in the description itself.

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?

With 100% schema description coverage, all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain format requirements, valid role IDs, or relationships between parameters. The baseline of 3 is appropriate when the schema carries the documentation burden.

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 action ('Add a wallet as a member'), target resource ('to an organization'), and specifies the role assignment ('with a specific role'). It distinguishes from sibling 'dual_remove_org_member' by being the complementary add operation, though it doesn't explicitly contrast with other organization-related tools like 'dual_create_organization' or 'dual_update_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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., organization must exist, wallet must be valid), doesn't specify when to use batch operations instead, and doesn't reference related tools like 'dual_create_org_role' for role creation or 'dual_list_org_members' for verification.

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