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

Annotations indicate this is a mutation (readOnlyHint=false) but non-destructive (destructiveHint=false). The description adds crucial context: it sets the sweepstakes to inactive, preserves all data, and blocks participant entries. It also mentions the prerequisite fetch_sweepstakes call, which goes beyond annotation data.

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 well-structured with headings and bullet points, but there is noticeable repetition: the opening paragraph and the 'When to use' section contain nearly identical sentences. This slightly reduces conciseness, though overall it remains clear and scannable.

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 one-parameter tool with no output schema, the description covers purpose, prerequisites, effect on participants, and data preservation. It is sufficiently complete for an agent to use the tool correctly without additional context.

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 schema provides 100% coverage, including a description for sweepstakes_token. The description adds value by explaining how to obtain the token via fetch_sweepstakes and confirming it is the unique identifier required for pausing, thus enriching the schema information.

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 clearly states the tool's function: 'Pause a sweepstakes, setting it to inactive status while preserving all data.' It distinguishes itself from destructive alternatives by emphasizing data preservation, and from unpause_sweepstakes by specifying the inactive status.

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 explicitly provides 'When to use' guidance, states the requirement to call fetch_sweepstakes first to obtain the sweepstakes_token, and notes that participants will not be able to enter while paused. This gives clear context for when to use the tool.

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