Delete Organize Link

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

Annotations already mark destructiveHint=true, and the description adds valuable context by specifying the destructive effect is limited to the sidebar link, not the target resource. It also flags the tool as experimental. This goes beyond the annotations without contradicting them.

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, front-loaded with the purpose and scope. The 'Experimental:' warning is concise and 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?

Given the tool's destructive nature and the presence of an output schema, the description provides adequate context about what is deleted and the level of impact. It doesn't explain return values, but the output schema covers that. It is sufficiently complete for a focused link-removal tool.

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?

Schema description coverage is 100%, with both parameters (nodeId, workspaceId) already documented with types and descriptions. The tool description adds no additional parameter-level meaning beyond what the schema provides, fitting the baseline of 3.

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 a specific verb ('delete') and resource ('AFFiNE organize doc, tag, or collection link node'), and further clarifies the scope ('removes only the sidebar link, not the target resource'). This distinguishes it from sibling tools like delete_folder or delete_doc.

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 implies usage (when you want to remove a sidebar link) and clarifies it does not delete the target, but does not explicitly state when to use this vs alternatives or provide exclusions. 'Experimental' hints at caution but is not a usage guideline.

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