添加机构学生

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

注解已声明非只读、非破坏且幂等，描述补充了关键前提（用户必须已注册）和返回结果，但未详细说明具体副作用、失败场景或权限要求。在注解基础上略有增益，但深度不足。

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?

描述结构紧凑，先说明主要功能，再列出参数和返回，易于快速理解。不过参数列表与schema冗余，但未造成臃肿，整体仍简洁高效。

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?

对于简单的添加操作，描述覆盖了核心行为、必要前提和返回结果，且注解和schema提供了额外的安全与参数信息。虽然没有输出schema或详细错误说明，但已足够支撑典型调用场景。

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覆盖100%，每个参数都有描述。描述中的参数说明基本与schema重复，未额外提供语义，如studentUid的特定格式或studentName的约束条件。因此保持基线3分。

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?

描述明确使用动词'添加'和资源'机构学生'，清晰表明功能是将已注册用户添加为机构学生。与兄弟工具（如添加课程学生、活动学生）能有效区分，因为指定了'机构学生'这一特定实体。

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?

描述仅说明操作本身，没有提供何时使用该工具、何时不使用或与替代工具（如classin_add_course_student）的对比。缺乏使用场景的指导，也没有排除不适用的情况。

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