move_note

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

Discloses the critical behavioral trait of direct SQLite write and app quit requirement, which annotations (none provided) do not cover. Does not detail error handling or side effects, but the key risk is communicated.

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?

Single sentence with no redundant information. All words are essential, and the critical information is front-loaded.

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?

Output schema exists, so return values are covered. However, the tool modifies data and requires app quit; the description does not state consequences of not quitting the app, error scenarios, or validation behavior. Incomplete for a destructive operation.

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 0%; the description only mentions note and notebook but does not explain the 3 parameters (note_id, notebook_id, dry_run). The dry_run parameter is completely undocumented, leaving the agent to rely on parameter names alone.

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?

Clearly states verb 'move' and resource 'note', distinguishing it from siblings like create_note, delete_note, update_note. Adds caveat about direct SQLite write and app quit, making the scope precise.

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?

Provides explicit context that it's a direct SQLite write requiring app quit, implying it should be used when the app is not running. No explicit alternatives mentioned, but the caveat informs when-to-use.

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