add_records

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions a constraint ('max 100 records') but doesn't disclose permissions required, whether the operation is idempotent, error handling, response format, or side effects. This is inadequate for a write operation 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 a single, efficient sentence with no wasted words. It front-loads the core purpose and includes a key constraint directly, making it easy to parse quickly.

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 write operation tool with no annotations and no output schema, the description is insufficient. It lacks details on permissions, response structure, error cases, and how it differs from similar tools like 'add_record'. Given the complexity of batch operations, more context is needed for effective use.

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 both parameters ('app' and 'records'). The description adds the 'max 100 records' constraint for the 'records' parameter, providing some extra context, but doesn't elaborate on data format or validation rules beyond what the schema implies.

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 action ('add multiple records') and target resource ('to a kintone app'), with a specific constraint ('max 100 records'). It distinguishes from 'add_record' (singular) but doesn't explicitly differentiate from other sibling tools like 'update_records' or 'get_records'.

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?

No guidance is provided on when to use this tool versus alternatives like 'add_record' (for single records) or 'update_records' (for modifying existing records). The description mentions a maximum record limit but doesn't specify prerequisites, error conditions, or typical use cases.

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