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

Annotations only declare readOnlyHint=false, so the description carries most of the behavioral burden and does add real value: enrollment is paid, the price is visible in game_university, and the action commits the player to a task-and-submit workflow. It stops short of stating failure conditions or whether enrollment can be undone.

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?

Two short sentences, no filler. The core action and its cost are front-loaded, with the follow-up workflow relegated to the second sentence.

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 single-parameter mutating tool with no output schema and minimal annotations, the description covers cost, parameter provenance, and the downstream steps needed to finish the quest. Only edge-case behavior (insufficient money, duplicate enrollment, failure response) is unaddressed.

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 0%, so the description must compensate, and it does by explaining that 'profession' is the number obtained from game_university rather than an arbitrary integer. It adds no format or validity detail beyond the schema's 1-25 range, but the origin of the value is the key missing piece and it is supplied.

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 — enrolling in a profession quest — and points at game_university as the source of the profession number. It does not explicitly name the related siblings (game_university_pass for handing in, game_university_refuse for declining), so differentiation is implied through the workflow rather than stated.

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?

It gives clear when-to-use context: pick the number from game_university, then complete the profession task in the journal and submit it at the university. There is no explicit when-not guidance (e.g., already enrolled, insufficient funds, cooldown), which keeps it from a 5.

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