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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description meaningfully adds that listed_discount is unconfirmed with verified_at null, and that max_price silently excludes deals with unknown price — a non-obvious filter side effect worth knowing. It says nothing about result ordering, result count semantics, or what mode does.

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?

Terse and front-loaded: the resource statement leads, then parameter semantics in a compact list, with no filler. Density is close to the limit — bare fragments like "unblock" and "limit 1-25" read as shorthand rather than prose, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and pagination plus price/offer-type filtering are covered. The significant remaining hole is mode (default "full") and the free-text filters query/category/tags, which are the primary levers for a search tool and are undocumented everywhere.

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% across 8 parameters, so the description must compensate and only partly does: it defines the offer_type value set, the max_price exclusion rule, the limit 1-25 bound, and the next_cursor→cursor paging loop (4 of 8). mode (default "full"), tags, query, and category get zero explanation in either schema or description.

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 ("Search agent work-stack deals") and enumerates the domain (compute, search, email, unblock, hosting), which is more than a restatement of the name. It never distinguishes itself from siblings like get_deal or compare_deals, so an agent must still guess which search/lookup tool to use.

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?

There is no explicit statement of when to use this tool versus get_deal, compare_deals, or optimize_stack. The offer_type list and pagination hint imply it is the bulk-listing entry point, but the agent has to infer that from context rather than being told.

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