remove_class_students

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

With no annotations provided, the description carries the full behavioral burden, and it does so thoroughly. It discloses the PS_ENABLE_WRITES requirement, the serialization constraint, the preservation of each student's other classes, and the refusal to empty a class. These details go well beyond a simple mutation statement and reveal important side-effect semantics.

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 front-loaded with the core purpose, then safety, then semantics, then argument definitions. Every sentence earns its place, and the warning about parallel writes is prominent and concise. It is appropriately sized for the complexity of the operation.

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?

Despite having no annotations, the description covers the critical invocation aspects: required permission, concurrency constraints, side-effect preservation, empty-class guard, and parameter sources. Since an output schema exists, the lack of return-value detail is acceptable. An agent has enough information to call this tool safely and 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 0%, so the description must compensate, and it does. It explains school_id as the student's school, section_id as coming from list_classes, and student_ids as coming from list_class_students, which gives the agent provenance for valid values. It also reinforces the required, non-empty nature of student_ids, adding meaning beyond the raw property definitions.

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 first sentence, 'Remove specific students from a class,' states a precise verb and resource, and the qualifier 'specific' distinguishes it from class-wide mutation tools like add_class_students or move_student_to_class. The subsequent guard 'student_ids is required: this tool will not empty a class' further clarifies exact 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?

The description gives clear context: it removes only specific students, preserves other class enrollments, and will not empty a class. It also provides a strong concurrency exclusion: never call it in parallel with other class-staff or student-enrollment writes. It does not explicitly name alternative sibling tools, but the behavioral context is enough to guide correct invocation.

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