Delete Note

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

No annotations are provided, so the description carries the full behavioral burden. It explicitly warns 'This permanently removes the note,' disclosing the irreversible destructive nature, and identifies the required input. It does not mention auth requirements or return behavior, but for a single-object delete operation the key risk is covered.

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 short sentences and a one-line 'Required' note convey purpose, risk, and the single parameter. No filler or redundant explanation.

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 simple one-parameter destructive tool, the description covers the essential action, the permanence warning, and the required note_id. With no output schema, it could optionally mention response behavior, but this is likely unnecessary for a standard delete operation.

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?

The input schema already describes note_id as 'The NoteId to delete' and marks it required; the description echoes 'Required: note_id' but adds no additional format, constraints, or origin information beyond the schema. With 100% schema coverage, this meets the baseline but doesn't elevate it.

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 opens with the verb 'Delete' and identifies the resource as 'a note from a contact's profile in Less Annoying CRM', clearly distinguishing it from sibling tools like get_note, edit_note, search_notes, and create_note. The destructive nature is explicit.

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 description states the tool deletes a note and warns that it permanently removes the note, giving clear context for when to invoke it. It doesn't explicitly name alternatives or provide when-not-to-use conditions, but the destructive warning sufficiently scopes the intended use.

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