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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' is redundant. However, 'Omits paymentDetails' is genuine value beyond the structured fields: it tells the agent the returned records are filtered/trimmed, which affects whether the result is sufficient for a financial query.

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?

Three tight, front-loaded fragments with no wasted prose. The only deduction is that 'Read-only' restates an annotation rather than earning its place.

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 3-param read tool with a fully documented schema and no output schema, the definition covers scope and one important return-shape caveat (omitted paymentDetails). It stops short of describing pagination behavior or the result shape, but nothing critical for correct invocation is missing.

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% – limit, cursor and farmId are each documented in the schema with ranges, defaults and cursor semantics. The description adds no parameter-level detail, which is acceptable here but leaves no added meaning.

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 (Supply Opportunity shipments) scoped to 'this farm', which lets an agent distinguish it from list_supplier_opportunities (opportunities, not shipments) and create_supplier_shipment. The parenthetical '(Financial Dashboard equivalent)' adds orientation but is slightly cryptic rather than clarifying.

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?

The word 'only' implies a contrast with a broader shipment listing, but no alternative tool is named and no condition for choosing this over a sibling is given. Usage must be inferred from the scope phrase rather than stated explicitly.

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