customer_notes_delete

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

Annotations already declare destructiveHint=true, so the description is not required to reiterate destructiveness. It adds the return format ({success}), which is useful, but does not describe other behavioral traits such as irreversibility or effect on related data. Given the annotations, the description provides minimal added context.

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 a single, succinct sentence that communicates the action and return value with zero unnecessary words. It is front-loaded and perfectly sized for the tool's simplicity.

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?

Given that this is a simple single-parameter delete with no output schema and strong annotations (destructiveHint=true), the description is nearly complete. It could optionally mention irreversibility, but the annotation already covers this. The return format is provided, so no critical information is missing.

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 schema description for the 'id' parameter already states 'Note ID to delete', and the description repeats 'by id'. Since schema description coverage is 100%, the description adds no new meaning beyond the schema. Baseline 3 applies.

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 uses the specific verb 'Delete' with the resource 'customer note' and the qualifier 'by id'. This clearly distinguishes it from sibling tools like customer_notes_list and customer_notes_create, making the purpose unambiguous.

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 clearly implies when to use this tool (when you need to delete a customer note by its ID). It does not mention alternatives or exclusions, but the context is clear from the verb and resource. For a simple delete operation, this level of guidance is sufficient.

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