add_member_event

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

Discloses that it returns a JSON confirmation or error, and that on success the API returns an empty body (HTTP 204). Annotations already show readOnlyHint=false, consistent with a write operation. No contradictions.

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 with no filler. Purpose is in the first sentence, usage guidance follows, then parameter details and return behavior. All sentences add value.

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?

Covers all five parameters, return behavior, and error conditions. With output schema existing in metadata, the description still adds context about the HTTP 204 response. Complete for a logging tool.

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?

Despite 0% schema coverage, the description adds detailed meaning for each parameter: list_id format and example, email_address derivation, name format constraints, and properties as optional dict. This fully compensates for the schema's lack of description.

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 tool records a custom event for an audience member, with examples like 'purchased'. It distinguishes from siblings get_member_events and get_member_goals by noting they are for reading.

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?

Explicitly states when to use: 'log member activity that can trigger automations or power segmentation'. Also specifies when not to use by referencing alternative tools for reading events and goals.

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