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

With destructiveHint already declaring the safety profile, the description still adds substantial context beyond annotations: open negotiations stop, buyers receive 'not found,' write-scoped Last Price credentials are required, and an unclaimed sandbox workspace is refused with 403. That is exactly the behavioral detail an agent needs before a destructive call.

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 short sentences, each front-loaded with useful content: effect first, then credential scope, then workspace prerequisites. No filler.

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 one-parameter, destructive, idempotent tool with no output schema, the description covers the effect, credential requirement, and workspace-claim refusal path. Nothing material 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 coverage is 100% for the single product_id parameter, so the schema already carries the meaning. The description adds no parameter-specific detail beyond that, so the baseline 3 applies.

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 a specific verb and resource: 'Take a product off offers.' The effect is unambiguous and clearly the inverse of the sibling set_offer_product, so an agent can distinguish the two without opening either 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?

The description explains consequences and prerequisites but gives no explicit when-to-use guidance or alternatives (e.g., when to use set_offer_product or a policy change instead). Usage is implied by the action rather than stated.

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