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

No annotations are provided, so the description carries the full burden. It does disclose the most important behavioral trait — that content overwrites the whole note rather than merging — but says nothing about partial-update semantics (does supplying only title preserve content?), permissions, or irreversibility of the overwrite.

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 that front-loads the primary action, then the secondary action, then the alternative. Every clause earns its place; nothing is padded.

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?

With no annotations and no output schema, the description should be self-sufficient, but it omits what happens when optional fields are left out, whether the note must already exist, and what the call returns. Adequate for the happy path, incomplete for a mutation tool with a destructive overwrite.

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 coverage is only 25% (only workspace is documented), so the description must compensate. It implicitly maps 'rename' to title and 'new Markdown content' to content, and clarifies replace-not-merge semantics for content, but leaves the optionality/partial-update behavior of title and content undefined.

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?

States two specific operations on a specific resource — rename a note, or replace its full text with Markdown — and names the sibling (append_to_note) it is not. An agent can distinguish it from append_to_note, create_note, and move_note without opening any 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?

Explicitly routes the append case to append_to_note, which is the most likely misuse. It does not address other adjacent cases (creating with create_note, relocating with move_note, or when to prefer get_note first to preserve content), so guidance is clear but not exhaustive.

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