edubase_post_user_organizations

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

Annotations are neutral (no hints). The description discloses that the tool can update existing memberships, indicating non-idempotence. However, it does not mention permissions, side effects, or response behavior, leaving gaps.

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 two sentences (13 words), no filler, and front-loaded with the core action. Every word is meaningful.

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?

Given the complexity (6 parameters, mutation tool, no output schema), the description is incomplete. It omits return values, error conditions, prerequisites, and behavioral context beyond the basic update behavior.

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%, with clear descriptions for all 6 parameters. The description adds no extra meaning beyond the schema, so baseline 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 action ('Assign user to organization(s)') and the resource ('user to organization'), with an additional nuance ('Updates membership if already member'). This distinguishes it from sibling tools like delete or get variants.

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 implies usage for assigning or updating user memberships but lacks explicit guidance on when to use this tool vs alternatives like edubase_post_organization_members. No exclusion criteria or prerequisites are mentioned.

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