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

Annotations already declare readOnly/idempotent/non-destructive, so the lower bar applies. The description still adds real context: the full shape of returned data (entries by day, top referrers, flagged entries) and the crucial fact that approval and drawing happen through dashboardUrl outside this tool, not via a write from the agent.

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?

Two sentences, no filler, and the payload contents are front-loaded ahead of the dashboardUrl note. Every clause either names returned data or clarifies an important side consideration.

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?

With no output schema, the description does the work of explaining what comes back, which is essential for this read tool. It could go further on auth requirements for dashboardUrl or behavior when the giveaway has not been drawn, but nothing critical for invoking it 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?

There is a single parameter with 100% schema description coverage, and the schema itself explains that giveawayId doubles as the campaign ID. The description adds no parameter-level meaning 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?

States a specific verb (Read) and resource (giveaway) and enumerates exactly what is returned: phase, approval, links, winners, entrants, entries, sources, top referrers, flagged entries. It is clearly distinct from list_giveaways by being a single-record read, though it never explicitly names the sibling.

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?

Usage is only implied: the singular giveawayId and the note that dashboardUrl is where a signed-in person approves or draws suggest this is the inspection/read step before a mutating action. It never states when to prefer this over list_giveaways or update_giveaway, nor any prerequisites.

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