课节批量添加学生

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

Annotations already indicate a write operation (readOnly=false), idempotent (idempotent=true), and non-destructive (destructive=false). The description adds batch context and the 500-student limit, which is useful. However, it does not clarify behavior when re-adding existing students or response details beyond '成功返回操作结果', so it contributes only modest value beyond 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?

The description is compact with a clear purpose statement and bulleted parameters. The '返回' section is vague but not wordy. It is well-structured and front-loaded, though the return description adds little value.

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?

This is a mutation tool with no output schema, and the description's return statement is too vague to be actionable. It also fails to mention the response_format parameter, which controls output type. However, the schema provides good parameter coverage and annotations give safety context, so it is minimally adequate for a simple batch-add operation.

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?

The input schema covers 100% of parameters with descriptions, including the response_format parameter which the description omits. The description simply repeats schema information for classId and studentUids without adding meaning (e.g., data types, examples, relationships). 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?

The description clearly states the action: '向课节中批量添加学生' (batch add students to class section), with specific verb+resource. It distinguishes from siblings by explicitly mentioning '课节' (class period) rather than course/activity/school, but does not name alternatives, so it lacks strong sibling differentiation.

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 provides no guidance on when to use this tool versus the many similar 'add_student' sibling tools (e.g., classin_add_activity_student, classin_add_course_student). There is no mention of prerequisites, exclusions, or alternative tool selection.

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