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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds a meaningful behavioral caveat — that results are 'conservative' and no synthetic composite score is fabricated — which shapes interpretation of output. It still omits whether optional sections are skipped or degraded when cultivar/soil inputs are absent, which matters for an orchestrating tool.

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 sentences with no filler, and the aggregation scope is front-loaded. However, the phrasing is dense with undefined internal terms, so brevity comes at the cost of comprehension rather than achieving efficient clarity.

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?

A read-only orchestrator with 11 parameters, a nested input object, no output schema, and zero schema descriptions demands far more explanation than is given. The agent cannot tell what soil_assessment accepts, how optional cultivar/rootstock inputs change the result, or what the combined response contains.

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 11 parameters, including a nested soil_assessment object, so the description must carry the load and does not. It never maps to a single parameter name (crop_id, lat/lon, cultivar_id, soil_ece, water_ec, soil_texture) or explains what the nested object should contain or what 'limit' caps. Vocabulary like 'environmental fingerprint' and 'cultivar evidence' gestures at inputs without disambiguation.

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 names the pieces being combined (environmental fingerprint, variety-fit, knowledge cards, soil assessment), so the aggregate intent is inferable. But it never states plainly what the tool returns or what a 'suitability' result is, leaning on internal jargon like 'canonical variety-fit' and 'reviewed cards'. An agent knows it aggregates several sub-analyses but not precisely what resource it produces.

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 statement of when this orchestrated call should be preferred over calling abiyar_variety_fit, abiyar_soil_assess, and abiyar_location_fingerprint individually, despite those siblings existing. The only guidance is a negative note ('does not invent a new composite score'), which doesn't tell the agent anything about selection.

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