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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that data is "live" from Matrix, implying fresh reads rather than caching, but says nothing about result size, pagination (the limit cap of 200), or what the returned taxonomy looks like, and there is no output schema.

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?

Two compact sentences with the resource and source front-loaded and nothing redundant. It is terse to the point of under-specification, but not padded.

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 simple two-parameter read tool whose annotations cover safety, the definition is close to sufficient, but with no output schema and zero parameter documentation the agent still doesn't know what a taxonomy record contains or how query matching behaves.

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 must carry the load, yet it only offers "optional query filters records" — it never says what field query matches (crop name, code, partial match?) or what limit controls or defaults to. Neither of the two parameters is meaningfully 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?

The description states a specific verb and resource ("Read ... Abyar crop taxonomy") plus its data source ("Matrix"), which distinguishes it from sibling abiyar_get_crop reasonably well. The term "Matrix" is unexplained jargon, keeping it from a 5.

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?

Says "Optional query filters records" but never states when to use this tool versus abiyar_get_crop or abiyar_describe, nor whether it should be called with no arguments to enumerate the whole taxonomy. No exclusions or prerequisites are given.

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