edubase_post_user_organizations

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

The description clearly states it creates or updates membership, which is appropriate since annotations indicate destructiveHint=false and readOnlyHint=false. The 'Updates membership' note adds transparency beyond annotations. However, it does not disclose what happens to existing permissions not specified (are they preserved or reset?), or whether the operation is reversible. Annotations provide basic safety info, so this is adequate but not comprehensive.

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 succinct sentences. The first states the primary action, and the second adds an important edge-case behavior. No extraneous words. While it could be slightly more front-loaded (the title already covers the first sentence), it is efficient and clear.

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 core purpose and an edge case, but is incomplete for a 7-parameter mutation tool with no output schema. It does not explain what the response looks like (success indicators, error conditions), what happens when required parameters are missing, or how the optional permissions interact (e.g., defaults are documented in schema, but not in description). Given the complexity and lack of output schema, more detail would be helpful.

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%, so the schema already documents all 7 parameters. The description does not add any additional meaning beyond what the schema provides. However, the param descriptions in the schema are fairly clear (e.g., 'optional name of department', 'comma-separated list of organization identification strings'), so the lack of extra description is acceptable. 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' and 'organization(s)'). It also clarifies edge-case behavior with 'Updates membership if already member of an organization.' This distinguishes it from sibling tools like edubase_get_user_organizations (read) and edubase_delete_user_organizations (delete), but does not explicitly contrast with edubase_post_organization_members, which might have similar purpose.

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. It does not mention when not to use it (e.g., if only reading memberships, use edubase_get_user_organizations), nor does it specify prerequisites (e.g., user must exist or have certain permissions). The description is silent on selection criteria among siblings.

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