Emit event

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

The description explains the enrollments array in the response, including the empty case. However, it does not disclose idempotency, side effects, or permission requirements. Annotations indicate non-destructive, but the description adds some value beyond them.

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?

Two sentences, to the point, no unnecessary information. Could be slightly improved by front-loading the core action, but overall efficient.

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 5 parameters, low schema coverage, and no output schema, the description is incomplete. It omits parameter semantics and usage constraints, making it insufficient for an agent to use correctly without additional knowledge.

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 description coverage is only 40%, and the description does not add meaning for email, userId, or traits parameters. It only mentions the name parameter implicitly. No additional guidance on parameter usage or relationships.

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?

Description clearly states the tool emits a customer event and explains the auto-enrollment behavior when sequences match. However, it does not explicitly distinguish from sibling tools like trigger_social_event or enroll_in_sequence, leaving some ambiguity.

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?

Provides context on when sequences will auto-enroll, but no explicit guidance on when to use this tool versus alternatives. No mention of prerequisites or exclusions.

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