add_member_note

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

No annotations present, so description fully carries the burden. It discloses authentication, concurrency (max 10), read-only/dry-run mode respect, and specific error responses (404, 400). This gives agent clear expectations.

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?

Well-structured with clear sections: purpose, usage, behavior, parameter list. Concise but covers necessary details. Could be slightly tighter, but no extraneous content.

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 purpose, parameters, errors, authentication, concurrency, and output structure. Missing mention of note ID for updates or limits on number of notes per member, but overall sufficient for selection and invocation.

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 0%, but the description provides detailed semantics for all three parameters: source of list_id, requirement that email exists, and note length/format restrictions (max 1000 chars, plain text). Fully compensates for missing schema descriptions.

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?

Clearly states 'Add a CRM-style internal note to a member. Not sent to the contact.' Verb and resource are specific, and it distinguishes from sibling tools like update_member_note by clarifying it's for new notes, not editing.

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 explicit use cases ('sales/support context') with examples, and directly advises to use update_member_note for edits. Also mentions obtaining list_id from list_audiences and that email must exist, guiding proper invocation.

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