Restore Note

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

With no annotations, the description carries the behavioral burden. It does disclose the key state transition: from trashed back into the vault. However, it does not mention edge behavior such as idempotency, what happens if the note is not trashed, or any permission requirements.

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 description is a single eight-word sentence that states the action and target immediately. It contains no filler and does not repeat schema 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 one-parameter tool with an output schema, the description covers the essential context: what operation is performed and on what object. It omits edge cases like restoring an already-restored note, but these are secondary and are likely reflected in output/error behavior.

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 has only one required parameter, note_id, and the description never names it. The phrase 'a trashed note' implicitly identifies note_id as the target note to restore, but the description does not explicitly elaborate on the parameter or its format.

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 names a specific verb ('Restore'), a specific resource ('a trashed note'), and a destination ('back into the vault'). This clearly distinguishes it from sibling create/delete/move tools because restoring from trash is a unique operation.

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?

The wording clearly implies the tool should be used when a note is trashed and needs to be returned to the vault. It does not explicitly list alternatives or exclusions, but the intended context is clear and unlikely to be confused with siblings.

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