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

Annotations already cover the read-only safety profile, and the description adds real context beyond them: the payload is largely collapsed-section UI state and won't be meaningful standalone. That warns the agent about noisy, low-signal data, which annotations cannot express.

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, with the core action front-loaded and the caveat immediately after. Nothing is wasted, though the caveat is hedged with a vague 'most of these' rather than a definite characterization.

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?

An output schema exists, so return values need not be explained, and there are no parameters to document. Given the simplicity, the description supplies adequate context, with only the absence of routing to get_user_profile as a gap.

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, so the baseline is 4; the description neither needs nor omits any parameter guidance. It does clarify the implicit scope ('this account's') rather than accepting a user identifier.

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 ('Get this account's Moodle user preferences'), so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from close siblings like get_user_profile, which keeps it from a 5.

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 note that most values are internal UI state implies this tool is low-value on its own, which is a useful implicit caution. However, it never states when to call it versus get_user_profile or other reads, and no positive use case is given.

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