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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the output is deliberately conservative and the fertilizer dose is withheld absent calibrated local evidence, which tells the agent to expect an incomplete result. It does not quantify that limitation or say what evidence would unlock the dose.

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 tightly written sentences, front-loaded with the action and immediately followed by the key caveat. No filler and no repetition of the tool name.

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 tool taking a free-form nested object with no output schema and no property documentation, the description does not explain how to build the assessment payload or what the screening result contains. The behavioral caveat is helpful but leaves the invocation guidance materially incomplete.

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?

The single required parameter 'assessment' is a nested object with zero schema description coverage, and the description says nothing about its expected shape or fields. With one opaque nested parameter, the agent has no guidance for constructing the call beyond guessing.

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: run Abyar conservative soil/lab/water screening. That is materially more specific than the sibling abiyar_water_need or abiyar_assess_suitability, but the description never explicitly names which sibling covers adjacent needs, so the boundary is inferred rather than stated.

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 explicit when-to-use clause, no prerequisite, and no named alternative such as abiyar_water_need or abiyar_assess_suitability. The agent must guess the screening context in which this tool applies.

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