edubase_post_organization_members

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

The description adds the update behavior ('Updates memberships if already member'), which is a useful behavioral trait not covered by annotations. However, it does not explain side effects like notification behavior or permission changes beyond what the schema provides, which is adequate given annotations already flag it as non-readonly.

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 extremely concise with two short sentences that clearly convey the primary action. No unnecessary words or repetition.

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 lacks information about the return value or response format. Since there is no output schema, this is a notable gap for an operation with 6 parameters and complex permission settings.

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?

Parameter descriptions are fully covered by the input schema with 100% coverage. The description does not add any extra meaning or context for parameters, so baseline score of 3 is appropriate.

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 tool assigns users to an organization and updates existing memberships, making the purpose unambiguous. It distinguishes from sibling tools like delete_organization_members and get_organization_members by specifying the action.

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?

No guidance is provided on when to use this tool versus alternatives, such as other post tools for user organizations. Prerequisites (e.g., existence of users or organization) are not mentioned, and the tool could be confused with edubase_post_organizations_members if that sibling exists.

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