apex_bulk_add_items

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

Annotations are neutral (readOnly=false, destructive=false) and provide no behavioral safety profile. The description adds no context about atomicity, partial failures, reversibility, or whether existing items are affected. For a bulk mutation, this is a significant transparency gap.

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 short and front-loaded with the core action. The field list is somewhat redundant with the schema and incomplete, but it is not verbose or padded. It earns a high score for efficiency, though not top marks because the list adds little value.

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?

With a detailed input schema and an output schema present, the description does not need to explain return values. However, for a mutation tool it lacks guidance on when to use it (vs single add), behavior on repeated calls, or error handling. The description is adequate but has clear gaps in context.

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%, so the input schema fully documents parameters. The description's field list ('name, type, label, lov, required, default') is a subset of the schema and omits optional fields like 'placeholder' and 'colspan'. It adds no new meaning beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb ('Add'), identifies the resource ('form items'), and distinguishes from the sibling apex_add_item by highlighting 'multiple' and 'in one call'. This is a clear, non-tautological purpose statement.

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?

Usage is implied by the name and description: use this for adding multiple items, unlike apex_add_item for single items. However, there is no explicit statement of when not to use it or a named alternative, so guidance is only implicit.

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