edubase_post_organization_transfer

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

Annotations provide readOnlyHint: false, destructiveHint: false, and openWorldHint: true, indicating mutation but not destructive. The description does not add behavioral context beyond the name and annotations. It does not disclose whether the transfer is reversible, what happens to the original owner, or whether any related data (e.g., members, permissions) is affected. Given the lack of annotation detail, the description should add more behavioral transparency.

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 (five words), which is concise but lacks necessary details. While brevity is valued, this description omits critical contextual information, making it feel under-specified rather than efficiently written. It could benefit from one or two more sentences to clarify usage and behavior.

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 has only 2 parameters with good schema coverage, and an output schema exists, so the baseline requirement is moderate. However, the description fails to explain what the transfer does (e.g., changes ownership, assigns admin rights), what user role is required (e.g., admin), or what the output contains. Without this information, an agent cannot reliably decide to invoke this tool.

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?

Although schema description coverage is 100%, the descriptions are generic: 'user identification string' and 'organization identification string'. These provide no additional meaning beyond the parameter names themselves. The description does not clarify the format of these IDs (e.g., are they numeric, UUIDs, emails?) or explain the semantics of 'user' in this context (e.g., is it the recipient user or the current owner?). The tool's job description offers no parameter-level details.

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 organization to user' clearly states the action (transfer) and the resource (organization) and target (user). However, it lacks specificity about the scope or effect of the transfer (e.g., does it transfer ownership, membership, or something else?). Among siblings, there are other transfer tools (e.g., edubase_post_class_transfer, edubase_post_exam_transfer) which follow the same pattern, so the description does not distinguish this tool from those.

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. There are many sibling tools for transferring various entities (e.g., class_transfer, course_transfer, exam_transfer). The description does not explain under what circumstances an organization should be transferred, or any prerequisites (e.g., user must be a member of the organization). No 'when not to use' or suggested alternatives are given.

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