bardo_link_add

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

Discloses mutation behavior (creating a link) and the lack of edit capability. No annotation contradictions; readOnlyHint false and destructiveHint false are consistent with creation.

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?

Three sentences, front-loaded with the main action. Every sentence adds essential information with no redundancy.

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 main purpose and param semantics. Lacks details on error handling or return values (no output schema), but adequate for a simple creation tool with clear annotations.

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?

With 0% schema coverage, description compensates by explaining the 'reason' parameter's perspective and 'is_bidi' meaning. Does not cover session_token, but context may imply it. Adds value beyond parameter names.

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 it connects two notes with a reason, from the perspective of from_note_id. Distinguishes from sibling tools like bardo_link_delete by focusing on creation.

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 guidance on when to set is_bidi (true for symmetric relations, false for directional) and how to modify links (delete and re-add). Implicitly contrasts with bardo_link_delete.

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