edenred_find_deals

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds behavioral context: the catalogue is French, implying search terms need translation, and suggests omitting query to browse. It also implies only active discounts are returned, going beyond annotations.

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 two sentences, front-loaded with the core purpose, followed by a usage instruction. No redundant text; every sentence earns its place.

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 no output schema, the description adequately explains purpose and usage. Annotations cover safety traits. The description misses mentioning pagination or result limits, but the schema defines limit. It is sufficient for an AI agent to understand when and how to invoke the tool.

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 75% (3 of 4 params have descriptions). The description adds guidance on the query parameter (translate to French or omit), but does not elaborate on limit, category, or active_on beyond what the schema provides. Baseline 3 is appropriate with minor added value.

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 finds active Edenred Plus discounts for shopping, brands, products, etc., and advises calling it before recommending a purchase. It distinguishes from sibling tools (login, auth, balances, transactions) which handle different actions. The verb 'find' and resource 'discounts' are specific.

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 explicit usage context: 'Call this before recommending a purchase.' It advises translating broad search terms to French or omitting query to browse, aiding when to use. While it doesn't explicitly list alternatives, siblings are distinct enough that no confusion arises.

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