app_custom_product_pages_delete_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. The DELETE method implies a destructive, likely irreversible operation, but the description never states whether deletion cascades to versions/localizations, whether the page must be in a particular state, what permissions are required, or what the failure modes are.

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?

It is very short, which is good, but the parenthetical '(DELETE /v1/appCustomProductPages/{id})' is a pure duplicate of the preceding text and earns no place. The only content is front-loaded, but there is little content to front-load.

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 destructive endpoint with no annotations, no output schema, and no explanatory prose, the definition is too thin. An agent needs at least confirmation that this permanently removes the custom product page and any caveats about associated versions before invoking it.

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?

There is a single parameter (id) and schema description coverage is 100%, so the schema already documents it as 'the id of the requested resource'. The description adds no syntax, format, or meaning beyond the path placeholder, which is the expected baseline when the schema does the work.

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 text states an HTTP verb (DELETE) and a resource path (appCustomProductPages/{id}), so an agent can infer it removes an App Custom Product Page. However it is a mechanical restatement of the tool name rather than a description of the operation, and the parenthetical duplicates the path verbatim instead of clarifying scope. Sibling tools like app_custom_product_pages_get_instance/update_instance are only distinguished by the verb embedded in the name, not by anything the description adds.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as app_custom_product_pages_update_instance or the version/localization delete tools that operate on sub-resources. The agent is left to infer entirely from the name.

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