Create Field Characteristic Value

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

Annotations already mark the tool as not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it creates a record and returns the created object, but no additional behavioral traits like authorization needs or side effects are disclosed.

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 two short paragraphs with a clear docstring-style parameter list. Every sentence adds value; no wasted words. Slightly structured but effective.

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 no output schema, the description states what is returned ('Created FieldCharacteristicValue with ID'), which is sufficient. The parameter list is complete. However, it could briefly mention constraints (e.g., characteristic configuration must exist) to be fully self-contained.

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 input schema is empty (0 parameters), so the description provides all parameter documentation: names, types, descriptions, and optionality. This fully compensates for the missing schema, giving the agent complete information to invoke the tool correctly.

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's purpose: 'Attach a characteristic value to a field' with specific example ('set an external plot ID or custom attribute'). It distinguishes from sibling tool 'sia_create_crop_zone_characteristic' by specifying 'field' in both name and description.

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 explains the tool's function and lists all parameters with types and descriptions. It does not explicitly contrast with siblings, but the context (field vs crop zone) is clear. A brief when-to-use note would elevate it to 5.

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