课节批量移除学生

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

Annotations already declare destructive and idempotent behavior. The description adds the batch size limit (max 500) and confirms the removal action. However, it does not describe side effects, error handling, or permission requirements.

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 brief and well-structured with a purpose statement, parameter list, and return note. No wasted words, though it is minimal.

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?

The tool has a destructive action, no output schema, and a vague return description ('操作结果'), leaving the agent uncertain about error handling and success details. Also, response_format is not mentioned in the description.

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?

All three schema parameters have descriptions, so the description adds little beyond the schema. It reiterates classId and studentUids but omits response_format. The 500-limit is already in the schema, so no additional semantic value.

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 tool's function: batch removing students from a class session (课节). The verb '批量移除' and object '学生' plus context '课节' distinguish it from sibling tools like classin_delete_course_student or classin_delete_course_class.

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 usage for batch student removal but does not mention alternatives or when to prefer this over other deletion tools. No exclusions or preconditions are provided.

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