get_mailing

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

No annotations are provided, and the description only states the high-level purpose. It does not disclose whether the operation is read-only, what response format to expect, or any potential errors or permissions. The word 'obtenir' implies retrieval but adds little beyond the tool name.

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 concise sentence that is easy to parse. No unnecessary words or repetition. However, it is somewhat under-specified, which prevents a perfect score.

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 simple get-by-id tool, the description is minimally acceptable but lacks detail. It does not specify that the response is a full mailing object, nor does it mention the required ID parameter. The absence of an output schema increases the need for clarity, but the description provides only vague 'details'.

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 input schema has one parameter 'id' (number) with no description, and schema description coverage is 0%. The description does not explain the meaning or purpose of 'id' (e.g., that it is the mailing campaign ID). This is a significant gap since the description must compensate for the schema's lack of parameter details.

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 'Obtenir les détails d'une campagne mailing' clearly states the action (get details) and resource (mailing campaign). It effectively distinguishes from siblings like list_mailings (which lists campaigns) and get_mailing_stats (which gets statistics).

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention that it retrieves a single campaign by ID nor when to prefer list_mailings or get_mailing_stats.

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