Delete Records

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates the destructive action and adds the maximum batch size of 100 records, but it does not mention irreversibility, permission requirements, or what happens if some records cannot be deleted.

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, front-loaded, and every sentence earns its place. It states the action, target, and a key constraint in only two short sentences.

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 simple batch-delete tool, the description covers the core operation and batch limit, while the input and output schemas supply parameter details and return structure. A slight gap is the absence of an explicit irreversibility warning, but deletion is strongly implied by the tool name and description.

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 description coverage is 100%, so the schema already documents all three parameters. The description does not add new parameter-level meaning beyond confirming the batch nature via the 100-record maximum, which is already present in the ids 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 states a specific verb (delete), resource (records), and container (a kintone app), making the tool's purpose immediately clear. It also distinguishes itself from siblings like kintone-update-records and kintone-get-records by focusing on deletion of records rather than other operations.

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 implies the tool should be used when multiple records need to be deleted from a kintone app, but it does not explicitly state when to prefer this over alternatives like kintone-update-records or kintone-delete-form-fields. No exclusions or alternative routing are provided.

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