create_mailing

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

With no annotations, the description must carry full behavioral disclosure. It only states 'create a mailing campaign'; it does not disclose whether the campaign is saved as draft, whether it is sent immediately, what side effects occur, or what authentication/permissions are needed. Creation implies mutation but lacks necessary context.

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, focused sentence with no filler or redundancy. However, its extreme brevity limits the information conveyed, so it is efficient but not maximally useful.

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?

No output schema and no annotations, so the description is the only source of context. It omits return values, expected parameter format (e.g., HTML body), and the lifecycle relationship to send_mailing. For a creation tool with five parameters, this is insufficient.

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?

Only one of five parameters (body) has a schema description, and the tool description adds no parameter information. It does not explain the meaning of title, subject, from_name, or from_email, nor clarify required fields beyond the schema's required list. With low schema coverage (20%), the description should compensate but does not.

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 names a specific action ('Créer' = create) and resource ('campagne mailing' = mailing campaign), distinguishing it from sibling tools like send_mailing, list_mailings, or get_mailing. It clearly indicates the tool creates a new mailing campaign rather than sending or retrieving one.

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?

No guidance on when to use this tool versus alternatives (e.g., send_mailing, list_mailings). It does not mention workflow prerequisites, such as needing to create before sending, nor any exclusions.

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