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

The description asserts a permanent, destructive, irreversible write ('Permanently delete', 'Cannot be undone'), while the annotations declare readOnlyHint=true and idempotentHint=true. This is a direct contradiction of the structured safety profile, which would badly mislead an agent deciding whether the call is safe.

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 sentence is short and front-loaded, but the parenthetical restates the same fact ('Permanently destroys a note you own') already conveyed by the lead clause, consuming space without adding information.

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 delete tool with no output schema, it covers permanence and the docking prerequisite, which is the core context. However, it omits error behavior, ownership failure modes, and confirmation semantics, and it is undercut by the conflicting readOnlyHint=true annotation.

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 description coverage is 100%, so note_id and session_id are already fully documented in the schema (including the permanence warning). The description adds no syntax or format information beyond what the schema provides, so the baseline of 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 states a specific verb and resource ('Permanently delete a note document you own'), which distinguishes it cleanly from siblings such as create_note, write_note, read_note and get_notes. An agent can identify the operation and its target without opening either schema.

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 discloses a precondition ('Requires docking') but never names an alternative or states when-not to use it versus write_note/read_note. Usage context is implied rather than routed, which is only minimally adequate.

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