Get Form Fields

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

Describes return structure (properties, revision) and support for live/pre-live. No annotations exist; description adequately conveys read-only nature without deeper constraints.

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?

Three well-organized sentences, front-loaded with purpose. Every sentence adds distinct information: purpose, return detail, and usage scenarios.

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?

Output schema exists; description sufficiently covers functionality and use cases. No gaps given tool's simplicity—reads as complete guidance for a retrieval tool.

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 has 100% coverage; description enriches by linking parameters to real-world use cases (e.g., preview for pre-live). Adds value beyond bare 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?

Clearly states it retrieves form field settings from a kintone app, with specific detail on returned info. Distinguished from sibling tools that add/update/delete.

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 frames the tool as essential before add/update/delete operations and for verifying lookup configurations. Lacks explicit when-not usage but provides strong guidance.

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