apex_list_dynamic_actions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds no behavioral traits beyond the operation itself, which is already implied by 'List'. No contradiction exists.

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, effective sentence, front-loaded with the verb and resource. It contains no extraneous words or redundancy.

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?

For a simple read-only list tool, the description, annotations, and schema are fully sufficient. An output schema exists, so return values are documented elsewhere. No critical context is missing.

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%, with both app_id and page_id having clear descriptions. The tool description adds no additional parameter meaning; it merely repeats the page scope already present in page_id. Baseline 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 'List dynamic actions on a page of an existing app' clearly states the verb (List), resource (dynamic actions), and scope (page of an existing app). It distinguishes from sibling tools like apex_list_items and apex_list_processes by naming the specific component type.

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 gives clear context: use this tool to enumerate dynamic actions for a specific page. It does not explicitly state alternatives or when not to use, but the context is strong enough and the sibling list provides natural differentiation.

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