assign_marketing_session

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

With no annotations, the description must disclose behavioral traits. It tags the action as a mutation and explains enable/disable, but it does not disclose side effects (e.g., impact on ongoing campaigns), required permissions, or reversibility. The agent lacks critical safety context for a write operation.

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 concise (one line) and front-loaded with the action. The [mutation] tag adds context. However, the dash separation is acceptable, and every word earns its place.

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 toggle tool, the description covers the basic action. But it omits error conditions, response format, and behavior on failure. Given no output schema and the sensitivity of mutating marketing settings, completeness is adequate but not thorough.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema; it merely restates the boolean parameter's purpose. No additional parameter context is provided.

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 verb ('assign'), the resource ('marketing session'), and the action ('enable or disable a WhatsApp session for sending marketing campaigns'). It distinguishes this tool from siblings that update sessions generally (update_whatsapp_session) or configure marketing globally (save_mass_marketing_config).

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 guidance on when to use this tool versus alternatives, nor does it mention when not to use it. It lacks context on prerequisites (e.g., session must exist) or exclusions. The agent is left to infer usage from the purpose alone.

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