edubase_post_integration_transfer

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the title (e.g., what happens to the previous owner, required permissions, or side effects). The description fails to disclose the implications of 'transfer' despite carrying the burden alongside sparse 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 a single concise sentence with no wasted words. However, for a tool with many siblings, slightly more context would be justified without sacrificing conciseness.

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?

Given the tool's simplicity (2 required string params) and the existence of an output schema, the description is still too brief. It does not explain the effect of the transfer (e.g., change of ownership, impact on permissions), nor does it help the agent distinguish this from the many other transfer tools. The description is adequate only for the most trivial use case.

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 clear parameter descriptions. The description 'Transfer integration to user' aligns with the schema but adds no additional meaning beyond what the field descriptions already provide (e.g., 'user identification string' and 'integration identification string'). 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 'Transfer integration to user' uses a specific verb ('Transfer') and resource ('integration') plus target ('user'), clearly distinguishing it from sibling transfer tools like edubase_post_class_transfer or edubase_post_exam_transfer.

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 (e.g., edubase_patch_integration or other transfer tools). There is no context about prerequisites, ownership changes, or when not to use it.

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