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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is covered. The description earns credit for disclosing what the payload contains — evidence, open conflicts, coverage, and rootstock-context policy — which is non-obvious and, absent an output schema, genuinely useful. It does not mention pagination or how conflicts are resolved.

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 dense sentence with the key noun phrase front-loaded and no filler. 'Rootstock-context policy' is jargon that costs a little clarity but the sentence is otherwise efficient.

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?

With no output schema and no parameter documentation, the description covers what is returned but leaves the agent guessing about crop_id provenance and limit behavior. Adequate to attempt the call, not complete enough to call it confidently on the first try.

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 must carry parameter meaning and it does not. Neither crop_id (format/source, e.g. from abiyar_get_crop) nor limit (default, max 50, effect on the returned list) is explained anywhere the agent can see.

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 (canonical rootstocks) scoped to a crop, and enumerates what the response carries (evidence, conflicts, coverage, policy). It is clearly distinct from assess_suitability or variety_fit, though it never names get_varieties, its closest cousin.

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 abiyar_get_varieties, abiyar_variety_fit, or abiyar_search_evidence. Usage is only inferable from the word 'List' plus the crop_id param.

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