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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: it names the return fields (name, seller, price text as shown by the seller, checked date, expiry, links) in the absence of an output schema, and it states the expired-offer default and the California-focused coverage.

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?

Three sentences, front-loaded with what is searched and what it spans, followed by filters and then output/exclusion rules. Dense and mostly waste-free, though the parenthetical focus note and return-field listing could be tightened slightly.

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 return-field summary is essential and present, and the expired-offer default is called out. For a 9-parameter read-only search tool the only notable gaps are pagination/limit behavior and result ordering, which an agent might want before calling it.

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 78%, so the schema already documents most parameters well, including the event format pointer to list_categories and the min_price caveat about offers without a single dollar price. The description only restates the filter set at a high level, adding no syntax, matching behavior, or edge-case detail beyond the schema, 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?

The description uses a specific verb and resource ("Search current JoinTheDeal deals") and defines the two content sets it spans: group deals sold by JoinTheDeal and Deal Finder offers on sellers' own sites, with a geographic scope note. It does not explicitly distinguish itself from the siblings get_deal or list_categories, so an agent must infer the boundary, keeping it short of a 5.

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?

It lists the available filter dimensions (keywords, category, event, seller, price range) which implies when to reach for it, and it explains the default exclusion of expired offers. There is no explicit guidance on when to use this instead of get_deal or list_categories, and no statement of prerequisites.

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