Delete Form Fields

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

With no annotations, the description discloses key behaviors: preview-only operation, 100-field limit, prohibited field types (status, assignee, category), and deployment dependency. It does not detail error handling or return values, but an output schema exists to cover the latter.

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?

Four sentences efficiently convey purpose, constraints, usage tips, and related tools. It is front-loaded with the main action and avoids redundancy, though could be slightly more compact.

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 the tool's complexity (deletion with restrictions, preview-only, deployment requirement), the description covers all essential aspects: environment, limits, prohibitions, workflow, and related tools. An output schema is present to document return values.

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% (3 parameters described), so baseline is 3. The description adds value by clarifying the maxItems constraint on fields and the revision checking behavior, plus listing prohibited field types not in schema.

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 deletes form fields from a kintone app in preview environment only, specifying verb 'delete' and resource 'form fields', and distinguishes from sibling tools like add, update, or deploy.

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 advises using kintone-get-form-fields first for verification, mentions the use case for recreating lookup fields, and notes that changes require kintone-deploy-app to apply to the live app, providing clear when-to-use and when-not-to-use guidance.

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