postmd_delete_note

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

With no annotations, the description must carry the behavioral disclosure. It mentions the required permission and the ownership restriction, which is helpful. However, it does not state that deletion is permanent, what happens to shared notes, or any confirmation behavior. For a destructive tool this is a partial disclosure.

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?

A single sentence with no filler. The main action and scope are front-loaded, and the permission requirement is included without unnecessary 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?

The description covers core purpose and permissions but lacks explicit parameter definitions and any mention of the return value or success/failure behavior. For a simple two-parameter delete operation, this is a moderate gap that an agent may need to infer from sibling note tools.

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 provides no descriptions for docCode or noteId, and the description never references these parameters directly. The property names are somewhat self-explanatory, and the ownership context implies a document-note relationship, but the agent gets no explicit parameter-level guidance.

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 verb ('Delete') and the resource ('a note'), and adds specific scope: your own note or a shared note on a document you own. This makes it easy to distinguish from note-related siblings like add, update, or resolve.

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?

It gives explicit conditions for when deletion is allowed, including ownership requirements and the required documents:write permission. Since there is no alternative delete-note sibling, no additional routing between deletion tools is needed.

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