b2_create_group_member

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

Beyond the annotations (destructiveHint, openWorldHint), the description discloses critical runtime behavior: secret handling differs by mode. It explains that file sink mode writes the one-time application key secret out-of-band and returns only redacted metadata plus a secretSink pointer, while inline mode returns the secret with an explicit warning. This is valuable, non-obvious behavior that annotations alone do not convey.

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 compact and front-loaded with the primary action, then efficiently explains the two secret-handling modes. Every sentence adds necessary information, and there is no filler or repetition of schema fields.

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?

The description covers the essential outcome, the secret-handling modes, and the response shape despite lacking an output schema. It leaves minor details such as failure behavior and billing implications unstated, but the schema and annotations fill most remaining gaps. Overall it is complete enough for correct invocation.

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 description coverage is 100%, so the input schema already documents all parameters including adminAccountId, groupId, memberEmail, idempotencyKey, region, and confirm. The description adds context about the generated one-time application key but does not add parameter-level meaning beyond the schema. Baseline 3 applies.

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 opens with a specific verb and resource: 'Create a Backblaze account for a new Partner group member.' This clearly identifies the operation and distinguishes it from sibling tools like b2_eject_group_member or b2_reserve_trial_create_account. The account creation intent is unambiguous.

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 gives clear context for when the tool applies: when a new Partner group member account must be created. It does not explicitly name alternatives or exclusions, but the context is specific enough that an agent can route to this tool for group-member creation versus other create/eject operations.

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