Create Crop Zone Characteristic Value

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

The description states it creates a resource and returns it with an ID. However, it does not disclose any behavioral traits beyond that, such as side effects, required permissions, or constraints. Annotations are all false and provide no additional context.

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: a one-line summary followed by a structured Args list and Returns line. No redundant information, every sentence is necessary.

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?

The tool is simple and the description covers parameters and return value. However, the input schema is empty, creating a contradiction that may confuse agents. The description is fairly complete in isolation but incomplete when reconciled with the schema.

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 description provides clear parameter names, types, and optionality despite the input schema being empty. This adds significant meaning beyond the schema, though no constraints or defaults are specified. The baseline for empty schema is higher, and the description compensates well.

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 explicitly states it attaches a characteristic value to a crop zone, with concrete examples such as number of trees. This clearly distinguishes it from sibling tools like sia_create_crop_zone (creates a crop zone) and sia_create_crop_zone_kpi (creates a KPI).

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 implies usage for attaching characteristics but provides no explicit guidance on when to use this tool versus alternatives like sia_get_crop_zone_characteristics (reading) or other create tools. The usage context is inferred rather than stated.

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