untag_note

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

Discloses important behavioral traits: direct SQLite write (bypasses app's API) and prerequisite that app must be quit. Adds context beyond the input schema, especially in absence of annotations.

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 of 15 words efficiently conveys verb, resource, method, and key constraint. No unnecessary content.

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?

Covers essential behavior and safety warning for a mutation tool with 3 parameters. Lacks detail on return values or error conditions, but output schema exists and succinctness is acceptable for this simple 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?

Adds nuance for 'tag' parameter (can be title or id) not present in schema, but does not describe 'note_id' or 'dry_run' beyond schema defaults. With 0% schema coverage, partial compensation.

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 the action 'Remove a tag' from a note, specifies that the tag can be identified by title or id, and distinguishes from sibling tools like 'tag_note'.

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 critical context that this is a direct SQLite write and the app must be quit, implying it should only be used when the app is closed. Lacks explicit mention of alternatives but gives strong usage constraint.

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