edubase_post_organization_members

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

Annotations indicate non-readOnly (write operation), non-destructive, idempotent false, openWorldHint true. The description adds behavioral context: it updates memberships if already a member (idempotency clarification) and assigns users. It does not contradict annotations. No details on side effects or auth requirements, but annotations cover safety profile well.

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?

Two sentences, zero waste. The first sentence states the primary action, the second clarifies idempotent-like behavior. Every word earns its place.

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?

With no output schema, the description doesn't explain return values, which is acceptable. Given 7 parameters (all described in schema), 3 enums, and complex permission fields, the description is complete enough for an agent to understand the core action. It could mention that permissions are optional and default values apply, but the schema already covers that.

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%, so baseline is 3. The description adds value by summarizing that the tool assigns/updates memberships, which contextualizes the parameters. It does not add detailed semantics for each param beyond the schema, but given full coverage, this is sufficient.

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 resource ('user(s) to an organization') and distinguishes itself from siblings like edubase_post_organizations_members by noting it updates memberships if already a member. However, the title is missing and the description could more explicitly contrast with other member-management tools.

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 when to use (assigning or updating memberships) but does not provide explicit guidance on when not to use this tool or mention alternatives among siblings (e.g., edubase_post_organizations_members, edubase_delete_organization_members). No exclusions or prerequisites are stated.

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