apex_add_item

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

The description briefly notes the auto-prefix behavior, but this is already present in the item_name schema description. It does not disclose additional behavioral traits such as permission requirements, reversibility, or the fact that it mutates the APEX app. Annotations are all false, so they provide no positive safety context. No contradiction is present, but the description adds little beyond the schema.

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, front-loaded sentence followed by a compact list of types. There is no redundancy or fluff, making it very efficient and easy to scan.

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?

Despite having 13 parameters and a rich schema, the description is too sparse. It does not mention required parameters, prerequisite that the region must exist, or important constraints like 'select requires lov_name'. The output schema covers return values, but for a tool of this complexity, the description leaves out key contextual information.

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% with detailed parameter descriptions, so the baseline is 3. The description adds minimal extra meaning; its type list is actually a subset of the schema's fuller enumeration, so it does not enhance parameter understanding beyond the 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 clearly states 'Add a form item' with a specific verb and resource, and lists item types. This distinguishes it from sibling tools like apex_update_item, apex_delete_item, and apex_bulk_add_items, making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives, such as apex_bulk_add_items or apex_update_item. It also omits prerequisites like the region must already exist (though the schema mentions this). This leaves the agent without explicit direction on tool selection.

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