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

The only annotation is readOnlyHint=false, so the agent already knows this mutates state; the description adds real value by disclosing the reward effect (the server issues the profession) and the completion precondition. It does not cover what happens if the assignment is unfinished or whether the action is reversible.

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?

A single sentence with no filler, front-loaded with the action, followed by the outcome condition. Nothing could be removed without losing meaning.

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?

For a no-parameter, no-output-schema mutation, the description covers both the action and its result, which is close to sufficient. It could go further by stating the prerequisite source (e.g. the sibling that provides or verifies the quest), but the essential call contract is present.

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?

There are zero parameters and 100% schema coverage, so no parameter explanation is required or possible. Baseline for a no-param tool is 4, but the description contributes nothing here, so a 3 is a fair neutral score.

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 names a specific verb and resource: handing in a profession quest at the university, with the server granting the profession. That clearly separates it from siblings such as game_university (entry point), game_university_enroll and game_university_refuse, though it never names those alternatives explicitly.

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?

Usage is only implied via the precondition 'при выполненном задании' (when the task is completed), which tells the agent the quest must be done first. There is no explicit statement of when not to call it, what happens on failure, or which sibling to use to obtain or check the quest.

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