save_note

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 says the note goes to a local text file but does not state overwrite vs create semantics (critical given the append siblings), filename derivation from title, permissions, or error behavior. For a write tool with zero annotation coverage this is a significant 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?

A single short sentence with no waste and the key fact front-loaded. It is efficient, though it is efficient at saying too little.

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?

A mutation tool with no annotations, no parameter documentation, and no stated overwrite/appending semantics. The output schema exists so return values need not be explained, but the write behavior itself is under-specified against a crowded sibling set.

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%, with two required parameters (title, content) documented only by their bare names. The description adds nothing about how title maps to a filename or how content is stored, and does not compensate for the coverage gap.

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 a specific verb (save) and resource (note to a local text file), which is clear enough. However, it fails to distinguish itself from siblings like append_note and append_response_to_note — the boundary between 'save a note' and 'append to a note' is exactly what an agent needs and is left unaddressed.

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?

No when-to-use guidance, no mention of alternatives, and no exclusions. With four sibling note tools, the description gives no signal for choosing save_note over append_note, which is a real selection risk.

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