edubase_post_event_transfer

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no behavioral context beyond what annotations provide, such as whether the transfer removes the event from its original user or if it triggers any side effects.

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 very short (one sentence), but it sacrifices clarity for brevity. It is under-specified and does not earn its place because it leaves out essential context. An effective concise description would be just slightly longer to include key details.

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?

Although an output schema exists, the description fails to explain the semantics of the transfer operation, such as what the input parameters represent beyond their schema names, any preconditions, or the nature of the output. For a tool with two required parameters and sibling ambiguity, the description is insufficiently complete.

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?

Both parameters (event, user) have descriptions in the input schema, providing 100% schema coverage. The description does not add additional meaning or constraints (e.g., format requirements, allowed values) beyond what is already in the schema. Baseline of 3 applies.

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 'Transfer event to user' identifies the verb (transfer) and the resource (event) and target (user), but it does not differentiate from sibling transfer tools like edubase_post_class_transfer or edubase_post_course_transfer. The term 'transfer' is ambiguous—it does not specify whether it changes ownership, moves membership, or reassigns the event.

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 alternative transfer tools. It lacks any context about prerequisites, typical use cases, or when another tool would be more appropriate.

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