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

Annotations already declare readOnly/idempotent/non-destructive and open-world, so the safety profile is covered. The description adds real value beyond them: results are paginated per 'vendor page' and login links plus arbitrary form fields are deliberately excluded, which warns the agent about missing fields.

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 tight sentences with no waste; the output content is front-loaded and the search/exclusion caveats follow in the right order.

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 usefully previews the returned fields (entrants, emails, entry/referral counts) and warns about exclusions. It is only short of page-size semantics and how to obtain the promotion_id, which are minor given the schema.

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 0%, so the description must carry the load; it explains page ('one vendor page') and query (email-address search), but says nothing about 'count' (page size, max 100) or the required promotion_id beyond its name. Partial compensation for a 4-parameter tool.

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 and resource: reading a page of promotion entrants with emails and entry/referral counts. The resource (entries) is distinct from siblings (brands, promotions, winners), so an agent can discriminate, though no sibling is named explicitly.

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?

Implies usage for pulling entrant data and notes the optional email search, but gives no explicit when-to-use vs. the other viralsweep_list_* tools and no prerequisites such as needing a valid promotion_id from viralsweep_list_promotions.

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