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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description does add genuinely useful, non-derivable context: results live in App Store Connect under Product Page Optimization, and the call is free (no credits). It still omits what the call actually returns or any pagination behavior.

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?

Three very short fragments, so nothing is bloated, but the structure is telegraphic and not front-loaded with a verb describing the operation. The sentence order puts the resource first and the cost note last, which is acceptable but not ideal.

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?

There is no output schema, so the description must carry the burden of explaining what is returned. It gestures at results existing in App Store Connect rather than stating that this tool returns the list of tests, leaving it ambiguous whether the tool returns test data or merely points elsewhere. For a listing tool with an undocumented parameter, this is insufficient.

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 description coverage is 0% and there is one parameter (appId). The description's phrase 'The app's' loosely implies app scoping but never explains appId, its expected format (numeric ID vs. bundle ID), or whether omitting it returns tests for a default/all apps.

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 identifies the resource domain (the app's product page tests / Product Page Optimization in App Store Connect) but never states the action. It relies on the tool name 'app_experiment_list' to convey that it lists tests, and gives no differentiation from siblings such as app_experiment_create or experiment_results.

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 and no mention of alternatives like experiment_results or experiment_create. The only usage-adjacent signal is 'Free.', which tells the agent the call has no cost but not when to prefer it.

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