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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: the default sort is end-date ascending and every result links out to an UltimateSweepers listing containing official rules, eligibility and the entry link. It omits rate limits or result-count behavior, but the added result-shape context is real value.

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, front-loaded with the core purpose and scope, followed by result-content context. No filler, no repetition of the title, and the default-sort fact is placed early where it matters.

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 nine-parameter, zero-required search tool with no output schema, the description supplies the scope, default ordering, and a sense of what a result contains. It could say more about result limits (the schema caps at 10) or lack of pagination, but nothing essential to calling it correctly 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 description coverage is 100%, so the schema already documents all nine parameters including the default sort order. The description's mention of the default end-date sort merely restates what the schema specifies, adding no syntax or semantics beyond it. Baseline 3 is appropriate.

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 (search) and resource (US sweepstakes) with tight scope qualifiers: free-to-enter, listed on UltimateSweepers.com. This clearly separates it from the singular retrieval (get_sweepstake), the category listing (list_sweepstakes_categories), and the write tool (submit_sweepstake).

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 when-to-use or when-not-to-use guidance is offered, and no alternative tool is named. It doesn't tell the agent when to prefer get_sweepstake (e.g., when an id is already known) or how this relates to the sibling tools, leaving usage to inference from the verb alone.

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