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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description still adds concrete value by spelling out what is destroyed ('the WHOLE service list... or what was there is wiped') and requiring user confirmation, which annotations alone do not convey.

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 tightly-packed sentences, front-loaded with the replace semantics before the destructive warning and confirmation step. No filler; each clause adds an actionable requirement.

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, open-world mutation with full param coverage and no output schema, the description supplies the workflow, the destructive consequence, and the confirmation gate. Nothing an agent needs to call it safely is missing.

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 100%, including the services, accountId, locationId and idempotencyKey params, so the schema carries the parameter burden. The description reinforces the 'COMPLETE list' semantics and structured-service format but adds no new syntax or format detail beyond what the schema states.

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?

Names a specific verb (replace), resource (the whole GBP service list), and scope (WHOLE list, structured-service format). This cleanly separates it from the closely-named sibling replace_gbp_food_menus and from update_gbp_listing, so an agent can pick it without opening the schema.

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?

Gives explicit preconditions and the alternative to reach for: read state with get_gbp_listing, then send the full list back with the change. It also states the consequence of skipping that step ('what was there is wiped') and adds a confirmation requirement, leaving nothing to inference.

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