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

The description discloses important behavioral traits not covered by annotations or schema, specifically the pagination behavior: 10 offers per response and a maximum of 5 pages. This is vital for understanding the operational limits of the search engine.

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 highly concise, using only two sentences. Both sentences are highly efficient, front-loading the scope and then defining the critical output limitations without any fluff.

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 the complexity of the 9 input parameters, the description is exceptionally complete by providing the regional scope, pagination details, and hard limits (5 pages max). This allows an agent to understand the tool's full functional boundary.

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?

Since the schema provides 100% description coverage, the description adds no meaningful semantic value to the individual parameters. It correctly meets the baseline score when structured data is exhaustive.

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 purpose: searching for open job offers ('Cherche dans les offres ouvertes'). It also establishes the geographical scope ('en France') and implicitly differentiates itself from the 'voir_offre' sibling by indicating a bulk search operation.

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?

While it does not explicitly say 'use this when X and not Y', it provides critical operational usage constraints (10 offers per response, max 5 pages). This information is essential for the agent to correctly manage expectations and sequence its calls relative to other tools.

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