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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description adds meaningful context: eligibility criteria ('reviewed, rights-eligible'), preserved provenance fields, and the special handling of San Angelo records (labeled, not counted as Central Texas member data). This is richer than annotations alone.

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?

The first sentence is front-loaded and does most of the work, but the passive, jargon-heavy phrasing ('rights-eligible', 'normalized classification dimensions') and the very specific San Angelo caveat make it dense. It is appropriately sized overall but not maximally clear or tight.

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?

An output schema exists, so return values needn't be explained, yet the description spends a sentence enumerating returned fields; meanwhile there is no guidance on the 8 undocumented input parameters, which is the more meaningful gap. For an 8-param tool with 0% schema coverage, the definition is only partially complete.

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 coverage is 0%, so the description should carry parameter meaning, but it only loosely maps a few fields (species via 'goat, sheep, or cattle', weight_band via 'source weight bands', class via 'normalized classification dimensions'). It says nothing about limit defaults/bounds, location syntax, purpose, breed_type, or weight_lb despite 8 parameters.

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 names a concrete output ('a bounded list of reviewed, rights-eligible published goat, sheep, or cattle observations') with a clear verb and subject, so an agent knows this returns livestock price records. It does not differentiate itself from siblings like get_market_report or get_usda_cattle_benchmark, leaving purpose clear but unbounded.

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 when-to-use guidance, no prerequisites, and no mention of the sibling tools (get_data_coverage, get_market_report, get_methodology, get_usda_cattle_benchmark) that an agent must choose between. Usage is only implied by the tool name and returned content.

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