Add Records

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

No annotations are provided, so the description carries the full burden. It discloses that some fields cannot be registered, but it does not mention permission requirements, error handling for partial failures, idempotency, or that this is a mutation (creating records). The description adds some value but lacks sufficient detail for a mutation tool.

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 concise sentences, front-loading the purpose. Every sentence provides essential information: action and prerequisite. No 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?

Given the detailed input schema and presence of an output schema, the description adequately covers the tool's job. It mentions unsupported fields and a prerequisite workflow. However, it could mention the record limit (100) which is only in schema, and lacks notes on error handling or performance.

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 type descriptions. The description adds value by advising to use kintone-get-form-fields for field codes and listing unsupported field types, which goes beyond the schema. This helps the agent avoid invalid parameters.

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 verb 'Add' and resource 'records to a kintone app', indicating it adds multiple records. It distinguishes from siblings like kintone-update-records (update) and kintone-delete-records (delete) by its action. The mention of using kintone-get-form-fields first also clarifies the tool's role in a workflow.

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 provides explicit guidance to use kintone-get-form-fields first to discover field formats and lists unsupported fields (e.g., LOOKUP copies, STATUS). However, it does not explicitly differentiate from alternatives like kintone-update-records for updating existing records or mention the max 100 records limit (though present in schema).

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