add_organization_member

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

With no annotations, the description must disclose behavioral traits. It only states the action ('Add a member') but omits details about side effects, required permissions, error handling, or whether the operation is idempotent. The agent cannot deduce if this is a simple mutation or has broader implications.

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, front-loaded sentence with no redundant words. However, it could be slightly expanded to include key context without losing conciseness, such as mentioning the expected structure of 'member_data'.

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 tool has a complex nested parameter and no output schema, yet the description lacks details on the structure of 'member_data' and the return value. It is incomplete for an agent to reliably invoke the tool without additional external knowledge.

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% with descriptions for each parameter. The tool description adds no extra meaning beyond the schema's own descriptions. The nested object 'member_data' is left undefined, which could be clarified but isn't required for a baseline score.

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 'Add a member to an organization.' uses a specific verb ('add') and clearly identifies the resource ('member') and target ('organization'). It effectively distinguishes from sibling tools like 'add_organization' (adds the org itself) and 'remove_organization_member' (removes a member).

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 does not mention prerequisites (e.g., the organization must exist), nor does it specify when it should be chosen over other 'add' tools like 'add_user_to_group' or 'add_realm_role_composites'.

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