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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds two genuine extras beyond the annotations: result ordering (newest first) and a UI locator (Office > Farm Notes). It says nothing about pagination behavior for cursor/limit or the size/shape of the returned set, so it is adequate rather than rich.

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 resource and scope front-loaded and no filler. The parenthetical UI path is slightly extraneous for an API consumer but is cheap and does aid disambiguation; nothing is padded.

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 list endpoint with no output schema, the description should at minimum explain how limit and cursor interact and what a returned page looks like, since the agent cannot learn that anywhere else. With zero parameter coverage and no output schema, the definition is under-specified for correct invocation despite the simple read-only nature of the tool.

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% across three parameters, so the description carries the full burden and mostly fails it. The phrase 'for this farm' loosely implies the farmId parameter, but 'limit' and 'cursor' — the pagination contract an agent must use correctly — are never explained in either the schema or the description.

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 states a specific verb and resource ('List Farm Notes') plus a scope qualifier ('for this farm'), which cleanly separates it from the singular get_farm_note and the mutating create_farm_note/update_farm_note siblings. However, it never names an alternative or explicitly distinguishes itself from those siblings, so it lands at clear-but-undifferentiated rather than fully self-routing.

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?

There is no guidance on when to use this tool versus get_farm_note or get_farm_note-adjacent siblings, and no mention of prerequisites such as needing a valid farmId. The ordering note ('Newest first') is output behavior, not usage guidance, so the agent is left to infer the calling context.

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