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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the endpoint and returned field inventory, but says nothing about pagination behavior, result ordering defaults, or how the silent-ignore filter behavior affects results.

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 terse fragments, front-loaded with the resource and its returned fields, then the endpoint. Zero wasted words and nothing buried.

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?

With no output schema, enumerating returned fields (title, type, size, status, grazing rest days) usefully compensates, and the schema fully carries the five optional parameters. Only minor gaps remain, such as what the paged envelope looks like and whether all listed fields are always present.

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 100%, so the schema already fully documents page, limit, filters, sort_by, and sort_dir, including the Farmbrite silent-ignore caveat. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (List) and resource (fields/grow locations), enumerates the returned fields, and gives the backing endpoint GET /plots. It is clearly distinguishable from farmbrite_get_plot, but never explicitly contrasts with it or with farmbrite_list_grazing_summary, so it stops short of full sibling differentiation.

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?

Only the implied 'list' semantics indicate when to use it. There is no guidance on when to prefer this over farmbrite_get_plot for a single plot or over farmbrite_list_grazing_summary for grazing data, and no stated prerequisites or exclusions.

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