apex_add_item_computation

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

The description only states the action ('Add') without revealing side effects, ordering implications, or reversibility. Annotations indicate readOnly=false and idempotent=false, but the description adds no further behavioral context such as whether repeated calls create duplicates.

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 one sentence and front-loaded with the main action. However, the parenthetical list is cryptic and could be expanded or removed, though it does not add unnecessary length.

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?

While the schema and output schema are rich, the description is quite minimal for a complex tool with multiple computation types and execution timing options. The schema covers parameter semantics, but the description does not provide high-level guidance on how computations fit into page processing.

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?

The input schema provides thorough descriptions for all 7 parameters, including the distinct computation types and execution points. The description does not add parameter details, but the baseline is satisfied by the high schema coverage.

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 tool's function as adding a computation to set an item's value, which distinguishes it from related tools like apex_add_item or apex_add_process. The parenthetical mention of computation types ('STATIC, SQL, PL/SQL, ITEM') provides a useful overview, though it is somewhat abbreviated.

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 explicit guidance is given about when to use this tool versus alternatives. The description does not mention common use cases, prerequisites, or why one would choose a computation over other mechanisms.

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