Update Form Layout

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

With no annotations, the description carries the full burden. It discloses the preview-only environment, case sensitivity of field codes, the required deploy step, and the nested structure for SUBTABLE fields. No contradictions.

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 at four sentences, front-loading the purpose and then providing key usage details and constraints. Every sentence adds value without 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?

The tool is complex with nested layout parameters, but the description covers the essential aspects: preview environment, prerequisites, case sensitivity, SUBTABLE structure, and the need for deployment. With an output schema present, return values are not required.

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%, so baseline is 3. The description adds value by explaining the nested structure for SUBTABLE and the case sensitivity requirement, which goes beyond the schema descriptions.

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 layout settings in a kintone app, specifically for the preview environment. It distinguishes from sibling tools like kintone-add-form-fields and kintone-update-form-fields by specifying 'update form layout'.

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 explicitly advises to use kintone-get-form-fields and kintone-get-form-layout first to understand the current structure, and notes that changes require kintone-deploy-app to apply. This provides clear when-to-use and post-action steps.

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