Update Form Fields

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

Given no annotations, the description adequately covers environment restriction, permissions, field code restrictions, side effects on selection fields, lookup update instability, and deployment requirement. Lacks mention of idempotency or rate limits, but overall strong.

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 a concise single paragraph with 8 sentences, front-loaded with purpose and scope. Every sentence adds value, covering limitations, warnings, prerequisites, and follow-up. No wasted words.

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?

For a complex tool with nested schema, the description provides critical context: preview environment, permissions, field code restrictions, option deletion, lookup instability, prerequisite, and deployment step. Output schema exists, so return values need not be explained. Highly complete.

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 100% with detailed descriptions for all parameters. The description adds minimal extra parameter meaning beyond noting which field types are restricted. Baseline 3 is appropriate.

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 updates form field settings in a kintone app, restricts to preview environment, and includes permission requirements. It distinguishes from siblings like add/delete form fields and notes prerequisite tool.

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?

Explicitly lists fields that cannot have their code updated, warns about unspecified options being deleted, advises against updating lookup fields without deletion/recreation, recommends using kintone-get-form-fields first, and notes the need for kintone-deploy-app to apply changes.

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