tag_note

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

Describes two modes (reuse existing entity or create new) and the structure of the entities argument. No annotations provided, but the description covers the core behavior well. Does not detail potential side effects like overwriting, but that seems unnecessary given the action.

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?

Concise: one-line purpose, one-line usage guidance, then two bullet-like arg descriptions. No redundant text, every sentence adds value.

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?

Fully covers the tool's operation with two params, no output schema, and moderate complexity. The description addresses both parameters and usage context, leaving no obvious gaps.

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 significant meaning beyond the input schema: specifies note format example 'note-3', details the entities object structure with id or name/kind/aliases, and lists valid kinds. Schema coverage was 0%, so description fully compensates.

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 'Link an existing note to the entities it references (resolving/creating each)', specifying the action and resource. 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?

Provides explicit use case: 'when you spot a subject in a note that wasn't tagged at capture time' and recommends prior resolution via 'list_entities'/'find_entities' to avoid duplicates.

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