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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds context the annotations do not: a uniqueness constraint per identity per note and an authenticity requirement that the caller must have witnessed the thing. It does not disclose what happens on a duplicate attempt or a failed precondition, which leaves a real gap.

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?

Three short sentences, each carrying a distinct rule (intent, cardinality, precondition), with no filler and the core action front-loaded. Nothing could be removed without losing a constraint.

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 simple two-parameter write with full schema coverage and annotations, the description covers the main preconditions. It is still thin on outcome: it does not say what confirming accomplishes, what a second confirm returns, or how the required session must be obtained, which matters because the tool is non-idempotent.

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 100% for both parameters, so the schema documents note_id and the session value from enter. The description adds no syntax, format, or origin detail beyond what the schema already states, which puts it at the baseline for a fully documented schema.

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 gives the verb ("Confirm") and the semantic intent ("that you observed the same thing"), but never names the resource being confirmed — the note is only identifiable from the title and the note_id schema field. An agent can grasp the intent but not, from the description alone, what object is affected or what effect confirmation has.

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?

"Only confirm what you saw yourself" is a genuine precondition that tells the agent when not to call, and "One per identity per note" sets a cardinality rule that bounds repeated use. It stops short of naming an alternative sibling (e.g. write or enter) for cases where the agent did not personally observe the event.

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