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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds only the endpoint path and the returned field set; it says nothing about pagination behavior or that unknown filters are silently ignored (that lives in the schema).

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?

A single terse sentence with the resource and output fields front-loaded; every token earns its place. It is arguably too thin rather than verbose, which affects other dimensions rather than this one.

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 read-only list endpoint with full schema documentation and clear annotations, the description covers what the tool is and what it returns. Minor gaps: no mention of pagination or that filters are supported, but these are documented in the schema.

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%, including detailed filter operator syntax and sort semantics, so the schema carries the parameter burden and baseline 3 applies. The description contributes nothing beyond naming returned fields, not the inputs.

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 livestock groups') and names the returned fields (id, name, type), which lets an agent distinguish it from farmbrite_get_livestock_group. It does not explicitly contrast with the singular fetch tool, 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?

No guidance on when to use this list tool instead of farmbrite_get_livestock_group, and no mention of the pagination or filter strategy despite those being the main usage decisions. The agent must infer usage from the name alone.

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