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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds beyond that: it discloses the reply shape (results plus next_offset) and the underlying endpoint GET /v7/harvest/blocks, giving an agent concrete expectations for a read call.

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 short, front-loaded sentences with no filler; the resource and its fields come first, then the conditional, then the return shape. The endpoint path is marginal but not distracting.

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 paginated list tool with no output schema, the description supplies the essentials: field scope, the include/vintage condition, and the paging reply shape (next_offset). Only the absence of any sibling routing or edge-case note keeps it from full marks.

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 all five parameters are already documented, including the include/vintage relationship and offset paging rule. The description restates the include+vintage pairing but adds no syntax or format detail the schema lacks — 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?

Specific verb plus resource and enumerated fields: 'List vineyard blocks (grower, vineyard, region, variety).' It is clearly distinct from vintrace_list_block_assessments in subject matter, though the description never explicitly names a sibling to route against.

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?

It gives one concrete usage condition — include fruitPlacements together with vintage to see fruit placements — which is genuinely helpful. It offers no when-not guidance and no comparison to sibling list tools such as vintrace_list_block_assessments.

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