Add Organize Link

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

The description adds valuable behavioral context beyond annotations: it flags the tool as 'Experimental' and warns about duplicate link creation for existing nodes. Since annotations already disclose read-only/destructive/idempotent traits, the description's additional context is sufficient. No contradiction with annotations is present.

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?

The description is only two sentences, front-loaded with the experimental warning and a clear verb. It conveys purpose, caveat, and alternative without unnecessary detail. Every word 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?

For a create operation with 5 parameters and an output schema, the description provides the essential selection and invocation context: what it does, the alternative, and a caveat. It doesn't explain return values, but the output schema exists. Slightly more detail on duplicate behavior could improve it, but it is complete enough for correct use.

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?

The input schema provides full descriptions for all 5 parameters (100% coverage), so the description does not need to explain parameters. It adds minimal extra meaning by mapping the 'type' enum to 'doc, tag, or collection', but this aligns with schema. Baseline 3 is appropriate as the schema handles the heavy lifting.

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?

The description clearly states the action (add) and the resource (a doc, tag, or collection link under an AFFiNE organize folder). It also distinguishes from the sibling tool move_organize_node by explicitly naming it, making the purpose unambiguous and well-differentiated.

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?

The description explicitly provides an alternative: 'Use move_organize_node for an existing link node instead of creating a duplicate link.' This clearly tells the agent when not to use this tool and what to use instead, exceeding the minimum requirement.

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