app_store_version_experiments_v2__update

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds a useful nuance about halting preserving readability, which goes beyond annotations, but it does not disclose other potential side effects like starting conditions or rate limits.

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?

Two concise sentences that front-load the main action, include an HTTP endpoint hint, and avoid unnecessary detail. Every word earns its place.

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 update tool with 100% schema coverage and no output schema, the description covers core behaviors and the important halt-vs-delete nuance. It doesn't explain the request body structure, but that is already in the schema.

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 schema only provides generic descriptions for id and body. The description's 'begin or halt' maps to the 'started' attribute and 'traffic split' maps to 'trafficProportion', adding meaningful semantics beyond the schema.

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's action: 'Change a product page experiment' with specific operations (begin, halt, adjust traffic split). This distinguishes it from sibling tools like create, get, or delete for experiments.

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?

It provides a usage distinction: 'Halting it keeps the results readable; deleting does not.' This hints at when to use update (to halt) versus delete, but does not explicitly enumerate all alternatives or scenarios.

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