edubase_post_classes_members

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

The description adds that it updates memberships if already a member, which is a behavioral detail beyond the annotations. However, it does not disclose other traits like authentication requirements, rate limits, or side effects, and the annotations already indicate it is not destructive or read-only.

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 with two sentences, front-loading the action and a key behavior. No superfluous text.

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?

Missing details about return values (no output schema), prerequisites, error conditions, and outcomes for optional parameters. For a mutation tool with 4 parameters, more context is needed for an agent to use it correctly.

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% with descriptions for all parameters, so the description adds no new meaning. The optional parameters 'expires' and 'notify' are not elaborated upon in the description.

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(s) to class(es)' and mentions membership update behavior. It is specific about the resource and action, but does not differentiate from the sibling tool 'edubase_post_class_members' (singular), which may have a different scope.

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 versus alternatives like 'edubase_post_user_classes' or 'edubase_post_class_members'. No context about prerequisites or exclusions is provided.

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