delete_contact_note

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

With no annotations, the description carries the full burden and does disclose the key traits: it is a destructive delete, it requires a named permission scope, and non-Admin callers are restricted to their own notes. It does not say whether deletion is reversible or how missing/inaccessible notes are reported, which keeps it below a 5.

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 definition restates itself (title line "Delete Contact Note" immediately followed by "Deletes a contact note.") and the trailing "Tags: Contact notes" adds nothing for an agent. The substantive constraints are present but not front-loaded ahead of the 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?

For a two-parameter destructive endpoint with no output schema, the description covers purpose, auth scope, role restriction, and the exact path, which is close to everything an agent needs to call it correctly. Reversibility and failure behavior are the only notable omissions.

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 100%, so both path parameters are already fully documented in the schema. The endpoint template shows where id and note_id sit in the path but adds no format or constraint meaning beyond that, warranting the baseline 3.

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?

States a specific verb and resource ("Deletes a contact note") and reinforces it with the concrete endpoint DELETE /api/v1/contacts/{id}/notes/{note_id}, which distinguishes it from deleting a whole contact. It never explicitly contrasts itself with the sibling delete_contact, so it stops short of a 5.

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?

The permission (contact_notes:delete) and role scoping (non-Admin agents may only delete their own notes) implicitly tell the agent when the call will succeed, but there is no explicit statement of when to choose this over alternatives or when not to call it.

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