apex_add_dynamic_action

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

Annotations are all false, so the description adds some context by stating it is a client-side event handler. However, it does not disclose behaviors like whether an existing DA with the same name is overwritten, whether changes are persistent, or any prerequisites such as needing an existing page or active app session.

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 purpose. It avoids unnecessary detail or repetition, making it 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?

Given the tool's complexity (13 parameters, TRUE/FALSE branches), the description is minimal. It does not mention the TRUE/FALSE branch concept, conditional execution, or prerequisites like an existing page_id or active app. The output schema exists, so return values are not needed, but the conceptual model is under-explained.

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 description adds little beyond what the schema already explains. The partial list of actions is potentially misleading: it uses 'submit' while the schema defines 'submit_page', and it omits other action types like 'enable', 'disable', and 'plsql'. This introduces inconsistency rather than adding value.

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 a dynamic action' and clarifies it as a 'client-side event handler', which directly distinguishes it from other 'apex_add_*' tools. Listing example action types reinforces the purpose without ambiguity.

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 implies when to use it (client-side interactivity) but does not explicitly state when not to use it or reference alternative tools (e.g., apex_add_process for server-side logic). It lacks explicit usage boundaries, but the context is reasonably clear.

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