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 returned-field inventory ('GET /grazings' is just the endpoint restated) but says nothing about result volume, pagination behavior, or whether a field with no grazing record is omitted or empty.

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 sentences, no filler, with the payload contents front-loaded ahead of the endpoint reference. Nothing needs trimming.

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 five optional params, all documented in schema, and no output schema, the description usefully enumerates the expected return fields, which partially substitutes for the missing output schema. It falls short only on paging/result-size expectations and on how grazing status relates to the plots/livestock-group tools.

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 page/limit/filters/sort_by/sort_dir are fully documented in the schema, including the filter operator syntax and the silent-ignore caveat. The description adds no parameter meaning of its own, which is acceptable at this coverage level but not additive.

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 (grazing summary), and itemizes the fields returned (animals present, days rested, rest days required, last grazed), including a clear per-field/per-pasture scope. It does not explicitly distinguish itself from list_plots or list_livestock_groups, which are the nearest siblings.

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 statement, no prerequisites, and no mention of alternatives such as listing plots or livestock groups if the agent instead wants the underlying entities rather than grazing status. Usage is only inferable from the resource name.

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