课程添加学生

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

Annotations already indicate this is a mutating, non-destructive, idempotent operation, so the description adds little beyond confirming it adds students. It does not disclose prerequisites, side effects, error conditions, or behavior when adding duplicate students. The generic '成功返回操作结果' adds no specific behavior detail.

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 succinct, with a clear purpose statement, parameter list, and return note. It is slightly redundant with the schema but remains free of fluff and well-organized.

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 is simple, and the schema is rich, but the description does not mention usage alternatives or error cases. It omits the response_format parameter behavior and does not explain the operation result. Adequate for a straightforward add operation but with gaps in guidance and edge-case transparency.

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%, and the schema provides detailed parameter meanings (e.g., courseId obtained from create course API, identity enum values). The description merely restates the parameter names and minimal meanings, adding no significant value over the schema.

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 it adds students or auditors to a course with the verb '添加' (add) and resource '课程' (course). It distinguishes from sibling tools like classin_delete_course_student and classin_add_activity_student by specifying the target resource as course rather than activity or deletion.

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 alternatives, no exclusions, and no context such as prerequisites. It simply states the action without explaining situations where this tool is appropriate or when to prefer a different tool like classin_add_activity_student.

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