apex_copy_page

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

Annotations indicate this is not read-only, but the description adds little beyond that. It does not disclose whether the target page ID must not already exist, whether associated regions/items are deep-copied, or what happens on conflict. The 'within the same app' claim contradicts the schema's allowance for cross-app copying, adding confusion rather than clarity.

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 sentence, which is concise, but it includes a potentially incorrect qualifier ('within the same app') and omits important behavioral context. Every word should add value; the 'same app' phrase actively detracts. It could be clearer and more accurate without being much longer.

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 copy operation with five parameters and an output schema, this description is incomplete. It does not explain the copy semantics (e.g., whether it is a deep copy, if target_page_id must be unused, or if related components are duplicated). The output schema may cover return values, but the operational behavior is under-specified.

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 descriptions for all parameters (100% coverage), including the optional new_page_name and target_app_id. The description itself adds no parameter-specific details and even misleads by implying same-app only. Thus it meets the baseline but does not enhance schema semantics.

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 a specific action ('Copy') and resource ('page'), with a destination ('new page ID'). It is distinguishable from sibling tools like apex_add_page or apex_update_page. However, it claims 'within the same app' while the input schema allows target_app_id to differ from source_app_id, which is misleading.

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 explicit guidance on when to use this tool versus alternatives (e.g., apex_add_page for new pages, apex_export_page for extraction). It does not mention prerequisites or scenarios where copying is preferred. Usage is only implied by the name and description.

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