cm_publish_event

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

The annotations only provide idempotentHint: false. The description adds no behavioral details beyond the basic purpose. It does not disclose potential side effects, whether the event is queued or immediate, or any required authentication/rate limits. This leaves the agent with minimal understanding of the tool's behavior.

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 sentence of 13 words, front-loading the essential information. No redundancy or unnecessary detail.

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?

Given the lack of an output schema and the presence of a nested object parameter, the description is incomplete. It does not explain what happens after publishing (e.g., return value, confirmation, event ID) or how the arbitrary Data payload is used. More context is needed for an agent to use this tool effectively.

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?

All four parameters have descriptions in the schema (100% coverage), so the description does not need to repeat them. The overall description adds context about 'Subscriber Activity event' but does not provide additional per-parameter semantics. Baseline 3 is appropriate.

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 action ('Publish'), the resource ('Subscriber Activity event'), and the purpose ('to trigger a journey for a client'). It sets the tool apart from siblings like send_campaign or send_smart_email, though it doesn't elaborate on what exactly a 'Subscriber Activity event' is.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites, limitations, or when not to use it. For example, it does not compare with cm_create_external_session or other journey-related tools.

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