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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the pagination contract ('Reply: results plus next_offset'), which matters because there is no output schema, but says nothing about filtering behavior, ordering, or whether block context is required.

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 clauses, front-loaded with purpose, followed by return shape and endpoint. The GET path is mildly redundant with the readOnly annotation but is compact and does not bury the important information.

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 six-parameter read-only list tool with no output schema, the description covers purpose and the paging reply but omits what an assessment record contains and gives no hint about how it relates to blocks, which matters since block selection is not a parameter.

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%, with all six parameters including the offset paging contract and the ext:/ne: prefix conventions already documented in the schema. The description adds no parameter meaning beyond that, so the 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?

States a specific verb and resource (list vineyard block assessments) and disambiguates the ambiguous noun 'assessments' with a parenthetical on vine/fruit assessments by the viticulture team. It is clearly distinct from the nearest sibling, vintrace_list_blocks, though it never says so explicitly.

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 guidance on when to call this versus related siblings like vintrace_list_blocks or vintrace_search_fruit_intakes, and no prerequisites or exclusions. Usage is only implied by the verb 'list'.

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