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

The annotations mark destructiveHint=false, but the description copies a complete configuration to a 'target tier to replace', implying the target's existing pricing and booking-policy settings are overwritten. This is a destructive side effect on the previous target configuration, so the description contradicts the annotations and fails to warn the agent about data loss.

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?

One tightly worded sentence conveys verb, object, source, target, and scope without unnecessary words. The core scoping constraint is front-loaded and every phrase adds meaning.

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?

An output schema exists, so return values do not need to be explained. However, for a mutating copy operation with a 'replace' target, the description omits the crucial warning that the target tier's existing config will be lost, and the annotation contradiction makes the tool's side effects misleading for an agent.

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?

All three parameters already have schema descriptions with 100% coverage. The tool description adds useful relational meaning: the copy preserves the complete pricing and booking-policy configuration and must stay on the same booking service, which enriches the field-level definitions.

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 states an explicit verb ('Copy'), exact resource ('complete pricing and booking-policy configuration'), and relationship ('from one membership tier to another on the same booking service'). This clearly distinguishes it from siblings like get_service_tier_pricing and set_service_tier_pricing.

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 gives clear context by requiring the same booking service and the source-to-target direction, but it does not explicitly say when to choose this over set_service_tier_pricing or get_service_tier_pricing. The intended usage is implied by the verb rather than stated.

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