Disable giveaway config

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds a rate limit (100 requests/10 seconds per shop), which is useful behavioral context, but it does not explain what 'disabling' entails (reversibility, effects on related resources), leaving a gap beyond 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 very short and contains no wasted words. However, it front-loads the rate limit note ahead of the purpose statement, which is a slightly suboptimal ordering for an agent scanning for what the tool does.

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?

Annotations cover the safety profile and the schema fully documents parameters, but the description omits what disabling a giveaway config actually does (e.g., stops checkout, revokes links) and the confirm parameter's role is only in the schema. For a destructive operation with no output schema, this leaves the agent without consequence details.

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%, so both parameters (account, confirm) are fully documented in the schema. The description adds no parameter information, which is the baseline expectation when the schema is complete.

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 'disables a giveaway config' restates the title 'Disable giveaway config' almost verbatim, providing no additional clarity about the action or distinguishing it from siblings like finish_giveaway or create_giveaway_checkout. It is a tautology rather than a specific purpose statement.

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?

No guidance is given about when to use this tool versus alternatives such as finish_giveaway or update_promotion. The description only states what it does, leaving the agent to infer usage context entirely.

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