Create Custom Product Page

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive. The description adds no additional behavioral context such as side effects, authorization needs, or rate limits. It is consistent but does not add value beyond 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, succinct sentence that conveys the core purpose without any wasted words. It is directly front-loaded with the action and resource.

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 creation tool with two required parameters and no output schema, the description is minimally adequate but lacks context about the relationship to other entities (e.g., app, localizations) and expected outcomes. It does not cover return values or prerequisites.

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?

With 0% schema description coverage, the description should compensate but only hints that 'name' is used ('named'). It provides no detail on valid values, uniqueness, format, or the role of 'appId'. The schema itself is minimal, and the description adds little semantic meaning.

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 creates a named custom App Store product page for targeted campaigns. It uses a specific verb and resource, and the context of campaigns adds purpose clarity. However, it doesn't explicitly distinguish from sibling tools like asc_update_custom_product_page or asc_create_custom_product_page_localization, which limits differentiation.

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 guidance on when to use this tool vs alternatives such as updating or listing custom product pages, or creating localizations/versions. There is no mention of prerequisites, conditions, or exclusions.

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