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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's '(read-only)' merely repeats the annotation rather than adding new context such as return format or scoping behavior; with annotations present, a 3 fits.

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 action/scope first, then the routing alternative. Every clause earns its place and the most important routing info is front-loaded.

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 simple single-parameter list tool whose annotations carry the entire safety profile and with no output schema required, the description covers the essential purpose and routing. The only gap is the undocumented farmId, which is minor at this complexity level.

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 description coverage is 0%, so the single required farmId parameter is undocumented everywhere. The description's 'this farm's' only loosely implies the farm scoping and never names or explains farmId or its format, so it fails to compensate for the coverage gap.

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?

Uses a specific verb (List) plus the resource (this farm's Academy enrollments/progress), and explicitly routes away from enroll_academy_course. It does not address the other nearby sibling list_academy_courses, but the resource nouns are distinct enough to disambiguate.

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 supplies the key when-not condition and the exact alternative: 'To enroll in a course, use enroll_academy_course.' It lacks an explicit 'use this when...' trigger (e.g. checking progress before enrolling) but gives clear context for routing.

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