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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the default append mode with a timestamped 'via AI' marker — but says nothing about the confirm/preview gate, the replace-overwrite risk, or the idempotencyKey dedupe behavior, all of which live only in the schema.

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 tight sentence with no filler, and it front-loads the most distinctive behavior (timestamped append by default). It is efficient, though the fragmentary phrasing means it never frames the overall operation.

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 7-parameter mutation tool with a preview/commit workflow, a replace-overwrite confirmation gate, and an idempotency key, one sentence is far too thin. Since no output schema exists, an agent gets no sense of what a successful edit returns or what the preview mode yields.

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 every one of the seven parameters is already documented with enums, defaults, and conditional requirements (confirmReplace for replace mode). The description reinforces only the append default and adds no syntax, format, or constraint detail beyond the schema, so the 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 conveys a specific action (appending a timestamped note) and a default behavior, but never names the resource it operates on — an agent must infer 'order' from the tool name. It reads more like a default-behavior footnote than a purpose statement, so the verb+resource pair is only half stated.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. farmId/orderId needed), and no reference to any alternative. The one sibling list contains no competing note-editing tool, so some of this burden is on the agent, but the description offers nothing about when this call is appropriate.

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