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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value by disclosing the filtering semantics ('canonical active') and the data source, but says nothing about ordering, pagination, or the shape/size of results.

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 front-loaded sentence with no filler and the scoping qualifiers ('canonical active') placed early. It is efficient, though the terseness leaves the identified gaps unaddressed.

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?

The tool is structurally simple (2 params, no output schema, strong read-only annotations), but with zero schema description coverage the description should explain crop_id format and limit semantics. It leaves both undocumented.

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 0%, so the description carries the full burden. 'For a crop' weakly signals that crop_id is a crop identifier, but neither the accepted crop_id format (pattern-constrained slug) nor the purpose of 'limit' (1-100, default behavior) is explained.

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 a precisely scoped resource ('canonical active cultivars/varieties for a crop'), plus the backing layer (D1-backed Abyar research). An agent can distinguish it from assessment-oriented siblings like abiyar_variety_fit, though no sibling is named 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?

No indication of when to call this versus abiyar_variety_fit, abiyar_get_taxonomy, or abiyar_get_crop. There is no statement of prerequisites (must the crop exist first?) and no exclusions; usage must be inferred from the word 'canonical active'.

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