edubase_post_organization_members

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

Annotations indicate the tool is not read-only and not destructive. The description adds that it updates existing memberships, which is useful. However, it does not disclose other behaviors such as error handling, authentication requirements, or idempotency (which is hinted as false via annotations but not explained).

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: two sentences front-loading the action and a key behavioral detail. Every word is necessary and no waste.

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 moderate complexity (6 params, 2 required, no output schema), the description minimally covers the operation but lacks details on return values, error cases, or the exact effect of the update. It is adequate but could be enhanced for completeness.

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 each parameter having a description. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate. It does not explain the format of users (comma-separated) or organization string beyond what schema says.

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 verb 'assign' and the resource 'user(s) to an organization', and notes the update behavior for existing members. However, it does not differentiate from the sibling tool 'edubase_post_organizations_members' which may have a plural nuance.

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 (e.g., edubase_post_organization_permission for setting permissions, or edubase_delete_organization_members for removal). No when-not-to-use or preconditions are mentioned.

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