Get Crop Zones

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

Annotations already confirm it's read-only, idempotent, and non-destructive. The description adds behavioral context by specifying default top=100, max results=500, and the OData filter format, but does not delve into error handling or pagination details.

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?

The description is extremely concise: a one-sentence definition of a crop zone, parameter details in two bullet-style lines, and a return type line. No superfluous content; every sentence serves a purpose.

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?

Given the low parameter count, rich annotations, and the description listing return fields (ID, name, isFallow, etc.), the tool is adequately documented for correct invocation. Missing details like field data types or error scenarios are minor gaps.

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 50% (filter has a description, top does not). The description compensates by explaining 'top' as max results with a default, and provides an example for 'filter' (e.g., "field_ID eq '<uuid>'"). This adds meaningful semantic context beyond the schema.

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 clearly states the action ('List crop zones from the SIA CropZoneService') and defines a crop zone, making it distinct from sibling tools like create or delete operations.

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 guidance is provided on when to use this tool versus alternatives such as sia_create_crop_zone or sia_get_crop_zone_characteristics. The description only explains what the tool does, not its context of use.

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