edubase_post_organization_members

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

The description adds useful behavior beyond annotations by noting that existing memberships are updated rather than rejected. However, it does not elaborate on side effects such as department reassignment or competency loss, which are only mentioned in schema parameter descriptions. Annotations already cover the read/write and destructive profile, so the description adds moderate value.

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: two sentences, no filler, and the primary action is front-loaded. Every word contributes to understanding the tool's purpose or behavior.

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 schema and annotations carry most of the required context: parameters are fully documented and the safety profile is declared. However, the description omits guidance about choosing this tool over the similarly named sibling edubase_post_organizations_members, and there is no output schema or return-value hint. It is adequate for basic invocation but incomplete for confident tool selection.

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%, and each parameter already has a meaningful description with enums and defaults. The tool description itself provides no additional parameter-level meaning, so it neither improves nor compensates beyond the schema, placing it at the baseline.

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 states a clear verb and resource: 'Assign user(s) to an organization.' This is specific enough to identify the tool's core function. However, it does not differentiate from the near-duplicate sibling edubase_post_organizations_members, so it does not fully distinguish itself.

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 no guidance on when to use this tool versus alternatives such as edubase_post_organizations_members, edubase_post_user_organizations, or edubase_delete_organization_members. It also does not mention prerequisites, typical invocation context, or when not to use it.

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