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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds useful content-level context (cards are 'reviewed' and carry source references and cautions), but says nothing about volume, pagination, or behavior when no reviewed cards exist for a crop.

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 waste, and the resource and returned content lead. It is arguably under-specified rather than over-long, but structurally it is clean.

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?

It tells the agent what the returned cards contain (evidence, sources, cautions), which partly compensates for the absent output schema. However, with five undocumented parameters and no guidance on filter behavior or result limits, it is not complete enough for confident invocation.

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% across 5 parameters, so the description carries the full burden and largely fails: only crop_id is implied. The limit, topic, status, and audience filters—including the meaning and allowed values of 'status' and 'audience'—are entirely unexplained anywhere.

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 ('read reviewed farmer/engineer knowledge cards for a crop') and names the content returned (evidence/source references, cautions). It does not differentiate itself from siblings like abiyar_search_evidence or abiyar_get_sources, which cover adjacent territory.

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 'reviewed' hints that only vetted cards are returned, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent choosing between this and abiyar_search_evidence gets no routing signal.

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