delete_member_note

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

Describes permanent nature, authentication via API key, max 10 concurrent requests, respect for read-only/dry-run modes, and 404 error on missing note/member. No annotations exist, so description carries burden effectively.

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?

Concise, well-structured description with a clear summary, usage hints, behavioral details, and parameter explanations. Every sentence adds value without redundancy.

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, prerequisites, parameters, return format, error handling, rate limits, and auth. No output schema exists, so the return description is essential and provided. Complete for a delete-note 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?

With 0% schema coverage, the description fully compensates by explaining each parameter: list_id obtained from list_audiences, email_address from member, note_id from list_member_notes. Adds actionable context beyond schema.

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 the tool permanently deletes a note attached to a member. Differentiates from similar tools like delete_member (which deletes the member itself) and add/update_note tools by explicitly noting it only affects the note.

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 guidance to use list_member_notes to obtain note_id before calling. Implicitly differentiates from siblings but does not explicitly list when not to use or alternatives.

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