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

With no annotations provided, the description carries the full burden of explaining behavior. It conveys a read-only search action without mentioning side effects, authorization, or return format. The lack of explicit non-destructive confirmation or pagination details is a slight gap, but the language 'search' and 'find' strongly implies a safe, read-only operation.

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, front-loaded sentence that efficiently communicates both the main action and key filters. No redundant words or filler; it earns its place entirely.

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?

The tool has four optional parameters, no output schema, and no annotations. The description gives a good high-level overview but does not mention what the result set looks like, whether pagination is supported (though 'limit' hints at it), or how results are ordered. For a read-only search tool, this is adequate but leaves some room for improvement.

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?

The schema already describes all four parameters with 100% coverage, so the description adds little new meaning. It does reinforce 'category' and 'budget' (mapping to category and maxPrice), but does not elaborate on limit or brandId beyond what the schema provides. 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?

The description clearly states the tool's function: searching for deals, discounts, and rewards across all brands with optional filters by category and budget. It distinguishes itself from sibling tools like rsnc_agent_brand_perks (brand-specific) and rsnc_agent_best_deals (curated picks) by emphasizing broad cross-brand discovery.

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 implies usage for browsing or discovering perks, especially when the user wants a broad search rather than brand-specific or targeted deals. However, it does not explicitly state when to use this tool over alternatives or provide exclusions, leaving the guidance somewhat implicit.

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