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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds genuinely non-obvious behavior on top: tasks are held under a 15-minute reservation and the returned work comes with caution instructions ("consignes de prudence"). It also discloses the operational constraints baked into the work (DMs bounded by a daily cap, campaigns entered in paused state). It does not explain what happens to a lease on expiry or how to release it (presumably report_browser_task), leaving a small gap.

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?

One compact sentence-group: audience first, then the work claimed, then the reservation/caution caveat. No filler, and the most decision-relevant facts are front-loaded. Note only that the description is in French while the schema, annotations and sibling names are English, a minor consistency wart rather than a length problem.

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?

For a mutating, no-output-schema tool the description is minimally adequate: it says what is claimed and that claims are time-boxed. It omits what the response contains (task payloads? lease ids? empty list when nothing is due) and leaves the filtering behavior of `limit`/`platforms` and the relationship to report_browser_task/complete_task to inference, which matters for an agent that must hand tasks back.

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 description coverage is 0%, so the description must carry the parameter meaning itself. The three example work types loosely map to the `types` enum (social_post, outreach_message, ad_campaign), but nothing explains `limit` (bounded 1-10) or `platforms`, nor whether omitted filters mean 'all types/all platforms'. With two of three parameters completely unexplained and the enum values not spelled out, compensation is only partial.

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 gives a specific verb+resource ("prendre les prochaines tâches") and enumerates the concrete work types claimed (publications to publish, DMs within the daily cap, campaigns to enter paused). It also names the intended actor (the agent driving the client's browser), which makes the tool's scope concrete. It stops short of naming how it differs from the sibling claim_task / claim_collection, so a 4 rather than a 5.

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?

"Pour l'agent qui pilote le navigateur du client" establishes a clear usage context and implies the tool is for automated browser workers rather than API-side publishing. However, there is no explicit when-not-to-use guidance and no pointer to the obvious alternatives (claim_task, claim_collection, report_browser_task) that a browsing agent would also call, so the routing must be inferred.

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