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

Annotations already convey that this is a mutating non-destructive operation. The description adds that the entire pricing and booking-policy configuration is copied, which is useful. It does not explicitly state that the target tier's existing configuration will be overwritten, though the schema parameter description 'Membership tier to replace' and the copy semantics imply it. No contradiction with 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 well-structured sentence that front-loads the action and resource, includes the key scope constraint ('same booking service'), and contains no filler or redundant information.

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 three-parameter tool with an output schema and full schema descriptions, the description is largely complete. It clearly states the operation and scope, though it could be slightly stronger by explicitly noting that the target tier's existing configuration is replaced.

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 input schema provides 100% parameter descriptions, so the schema already carries the semantic weight. The description adds the useful context that the configuration being copied is 'complete' and 'pricing and booking-policy', but it does not need to add more per-parameter detail beyond what the schema provides.

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 uses a specific verb ('Copy') and identifies the exact resource: the complete pricing and booking-policy configuration between membership tiers on one booking service. This clearly distinguishes it from sibling tools like set_service_tier_pricing and get_service_tier_pricing, which set or retrieve rather than copy.

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 implies when to use the tool: when the agent needs to duplicate all pricing/booking-policy configuration from one tier to another. However, it does not explicitly state when not to use it or name the alternative set_service_tier_pricing for partial updates, leaving some routing to inference.

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