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

The readOnlyHint already declares this is a safe read, so the description's main added value is the situational constraint 'inside building type 18'. It does not say what happens if the player is not in the building or not enrolled, nor whether the response varies by profession.

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 compact sentence with the location prerequisite front-loaded and the returned data enumerated. Slightly dense listing separated by commas, but no wasted words.

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 parameterless read with no output schema, it does state the location requirement and the categories of data returned. Only failure modes and gating conditions (student status, profession availability) are left unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The phrasing correctly implies a single parameterless lookup that returns multiple data points.

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?

Names the resource (university) and enumerates what it exposes: enrollment price, profession menu, and the current profession quest. It is clear this is an information-read tool rather than the enroll/pass/refuse sibling actions, though the distinction is implied 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?

Usage is implied by the fact that it only reports price/menu/quest data, so an agent can infer it should be called before game_university_enroll. No explicit when-to-use, prerequisites (e.g. being a student), or named alternatives are given.

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