Get Crop Zone Characteristic Values

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that it returns an array of objects and gives example filter syntax, but does not elaborate on pagination behavior, sorting, or rate limits. Some value added beyond annotations.

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 concise with a clear introductory sentence and a bulleted Args/Returns structure. Every sentence serves a purpose with no redundancy.

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?

With no output schema, the description states the return type but does not detail the fields of CropZoneCharacteristicValue objects. However, the tool has simple parameters and annotations cover safety, so it is mostly complete for a read-only listing tool.

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%, and the description adds a concrete filter example and clarifies the default for top. This goes beyond the schema's minimal description for filter, but the schema already provides type, min, max, and default for top.

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 tool lists characteristic values attached to crop zones, with examples like tree counts and custom attributes. This verb-resource combination distinguishes it from sibling tools like sia_get_crop_zones (which returns zones) and sia_get_field_characteristics.

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 description provides an example filter but does not explicitly state when to use this tool versus alternatives like sia_get_characteristic_configurations or how to decide between filtering and pagination. Usage context is implied but not clearly bounded.

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