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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes beyond them by disclosing the status taxonomy the caller must interpret and the mandatory two-step browser-task protocol for social channels. That is real behavioral context an agent cannot get from the schema or 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?

Four short sentences, front-loaded with the result shape before the id rule and then the platform-specific caveat; nothing is redundant. The telegraphic style and French/English mix make it slightly harder to parse than necessary.

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?

There is no output schema, so the description must convey return semantics, and listing the possible statuses does that adequately for a single-parameter read tool. What remains thin is the id format and whether results cover one recipient, one step, or many.

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?

With schema description coverage at 0%, the description must carry the parameter meaning, and it does explain the id's provenance (returned by the step). It says nothing about the id's expected format or scope (step vs run vs recipient), so compensation is 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 states it returns per-recipient results for a communication step and names the four statuses (queued, to validate, awaiting MonAssocié, sent), which makes the resource concrete. It does not explicitly contrast with siblings such as describe_workflows or get_workflow_app_watch, so differentiation is left to the tool name.

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?

It gives a clear precondition — 'Utiliser l'id retourné par l'étape' — and adds a procedural rule for LinkedIn/Facebook/Instagram/TikTok: call claim_browser_tasks first, then report_browser_task after real execution, attachments included. No negative cases or sibling alternatives are stated, so it stops short of a full when/when-not guide.

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