tag_note

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

Discloses direct SQLite write and app quit requirement, which are essential behavioral traits beyond schema. No annotations present, so description carries burden.

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?

Two sentences, no fluff. Front-loads purpose then adds critical operational info. Every sentence earns its place.

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 core behavior and crucial operational constraint. Has output schema, so return values need not be described. Missed dry_run parameter explanation.

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?

Describes 'tag by title or id' and 'creating if needed' (matches create_if_missing), but does not explain dry_run parameter. 0% schema coverage requires more description.

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?

Explicit verb 'Add', resource 'tag to a note', with key behavior 'creating the tag if needed'. Clearly distinguishes from siblings like untag_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?

States 'Direct SQLite write; the app must be quit', providing critical operational guidance. No explicit alternatives mentioned, but context is clear.

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