Delete Note

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

The description adds the idempotent-when-missing behavior, which is valuable beyond the destructive annotation. It does not explain other effects like cascading deletions, but the idempotency detail is a meaningful addition.

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 two sentences with no unnecessary words. It efficiently conveys the action and an important behavioral trait.

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?

The tool has two required parameters and no output schema, but the description only partially covers those. It explains the action and idempotency but leaves profileId semantics and any response/return value unaddressed, making it minimally adequate.

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 description coverage, the description must compensate by explaining parameters. It mentions the note ID as the deletion target but completely omits the required profileId parameter, leaving its role unclear.

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 clearly states the tool deletes a note directly by note ID. It distinguishes itself from the sibling batch delete tool by focusing on single-note deletion.

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 gives clear context for direct single-note deletion and notes idempotency, implying it is safe to use for retry scenarios. However, it does not explicitly mention when to use the batch alternative or any exclusions.

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