edubase_delete_user_organizations

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

Annotations already provide destructiveHint=true and idempotentHint=true. Description adds no further behavioral context (e.g., cascading effects, required user permissions, or whether relationships beyond membership are affected). It doesn't contradict annotations.

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?

Extremely concise: a single sentence of 5 words. No fluff or redundancy. 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?

Simple tool with 2 required params and no output schema, but description lacks scope details (e.g., 'Remove user from one or more organizations? Completely or partially?'). Returns/consequences are not mentioned. Incomplete for guiding an agent on expected outcomes.

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 parameters are already documented. Description adds no additional meaning about 'user' or 'organizations' beyond their schema descriptions (e.g., no format, validation rules, or constraints). 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?

Description clearly states verb (remove) and resource (user from organization(s)). It's concise and unambiguous, distinguishing its destructive removal purpose from sibling tools like edubase_post_user_organizations (add) and edubase_get_user_organizations (list).

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 on when to use this tool vs alternative removal methods (e.g., edubase_delete_organization_members or edubase_delete_user_classes). No prerequisites or conditions for removal are mentioned.

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