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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read-only' is largely redundant. The description does add non-annotation value by disclosing the category exclusion and that results carry price/freeForTiers hints, which tells the agent what the payload will contain.

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?

Three terse, front-loaded fragments with no filler; the scope constraint and the read-only/safety note come early. The telegraphic style is efficient, though it reads as a note rather than a 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 simple two-parameter, optional-argument list tool with rich annotations and no output schema, the description covers scope and payload hints adequately. It is incomplete on the undocumented 'limit' parameter and on result-size/pagination behavior, which an agent would need to call it confidently.

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 only 50%: farmId is documented in the schema, but 'limit' has no description anywhere. The description mentions price/freeForTiers hints (an output trait) but says nothing about what limit controls, its default, or pagination, so it does not 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?

States a specific verb and resource ('List published QuailOS Academy courses') plus a scope constraint ('excludes Rent-a-Hatch category'), so the agent knows it returns a curated catalog rather than everything. It does not name the closely related siblings get_academy_course or list_my_academy_enrollments, so differentiation is only implicit.

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?

No when-to-use or when-not-to-use guidance is given; the agent has to infer that this is the browse-the-catalog entry point versus get_academy_course (single course) or list_my_academy_enrollments (personal). The 'excludes Rent-a-Hatch' note is scope, not routing guidance.

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