slickdeals_search

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

With no annotations, the description carries the full burden of behavioral disclosure. It details the return structure (each result's fields), explains that the best-effort price is extracted from the title, and notes that both filters are closed enums validated before the request reaches upstream. However, it does not mention pagination, rate limits, authentication, or potential errors, leaving notable gaps for a search tool.

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?

The description is a single dense paragraph, but it is well-structured: it leads with the core purpose, then describes the results, follow-up actions, and filter details. While it is not brief, every sentence contributes information, and the flow is logical. It could be split for readability, but it is not bloated.

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?

Given that there is no output schema, the description effectively communicates what a result contains (title, price, merchant, thumb score, username, post time) and how to obtain full details via the deal endpoint. It also explains the optional filters and their sourcing. It omits pagination and result ordering, but for a keyword search tool with these parameters, the essential information is present.

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 100%, but the description adds meaningful value beyond the schema: it explains that forum_id and deal_type_id are closed enums validated before the request, specifies that values must come from specific endpoints (GET /slickdeals/forums and /slickdeals/deal-types), and notes that the two filters compose. This goes beyond simple restatement and aids correct parameter selection.

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 clearly states that the tool searches Slickdeals community-submitted deals by keyword, specifying the resource (Slickdeals deal threads) and the action (free-text keyword search). It also differentiates from other search tools by referencing the existing Reddit search functionality and mentions the specific resource it applies to. The verb and resource are unambiguous and distinct from sibling tools.

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?

The description provides actionable usage context, such as how to pair results with the deal detail endpoint and where to obtain valid enum values for forum_id and deal_type_id. However, it does not explicitly state when to use this tool versus alternatives like slickdeals_search_advanced, nor does it provide conditions for preferring one over the other. The guidance is implicit rather than explicit.

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