edubase_post_exam_transfer

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

Annotations already indicate a non-readonly (write) operation and non-destructive hint. The description adds only the verb 'Transfer' without explaining what that entails—e.g., does it change ownership? Affect previous owner? Require both users to belong to the same organization? No behavioral details beyond the annotation level.

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 a single sentence with no wasted words. However, it could be more informative without losing conciseness by including constraints or outcomes.

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 an output schema (content unknown), 2 well-described parameters, and annotations, the description fails to explain what the transfer operation actually accomplishes, what side effects occur, or what the response signifies. For a mutation tool, this is incomplete.

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 100%, with 'exam identification string' and 'user identification string' descriptions. The description adds no additional meaning for these parameters beyond what the schema already provides, so the baseline score of 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 states the verb 'Transfer' and the resources 'exam' and 'user', making the core action clear. However, it does not differentiate this transfer from sibling transfer tools (e.g., class, course, quiz) which share the same pattern, so the nuance of 'exam transfer' is missing.

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?

No guidance is provided on when to use this tool versus alternatives like edubase_post_exam_users or other transfer tools. Prerequisites, such as whether the user must already exist or have specific permissions, are absent.

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