apex_add_process

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

With all annotations set to false, the description carries the full burden of behavioral disclosure, but it only states 'Add' with no mention of side effects, permission requirements, idempotency, or impact on existing processes. It does not contradict annotations.

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 that efficiently conveys the core action. However, it is arguably too terse for an 11-parameter tool with multiple process types, but it remains concise and ordered.

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?

Given the tool's complexity (11 parameters, multiple process types, page context), the one-sentence description is inadequate. It does not mention the need for page_id, how process_type interacts with other fields, or any return/result behavior. This is a significant gap.

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?

Although schema coverage is 100%, the description's high-level summary ('PL/SQL block, DML on table, or branch redirect') is partially inaccurate and omits process types like 'ajax', 'close_dialog', and 'clear_cache'. It fails to add value beyond the schema and potentially misleads.

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 identifies the tool as adding a page process, but the listed process types ('PL/SQL block, DML on table, or branch redirect') are incomplete and include 'branch redirect' which is not among the schema's process_type enum values (dml, plsql, ajax, close_dialog, clear_cache). This introduces ambiguity about what the tool actually supports.

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 apex_add_app_process. It does not specify that it operates on a specific page, nor does it mention any prerequisites or exclusions.

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