Add Organize Link

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

No annotations. Only the 'Experimental' label is mentioned; no disclosure of side effects, permissions, or failure behavior. As a mutation tool, this is insufficient.

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?

Extremely concise (one sentence), but at the cost of missing critical details. It front-loads the core action but lacks efficiency of communication.

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 no output schema and low schema coverage, the description is incomplete. Missing details on index behavior, folder existence prerequisites, or link semantics.

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 coverage is 40% (only targetId has description). The description does not add meaning for workspaceId, folderId, type, or index. Fails to compensate for low schema coverage.

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 states 'add a doc/tag/collection link under an AFFiNE organize folder', clearly indicating the verb and resource. It distinguishes from siblings like 'delete_organize_link' and 'move_organize_node', though 'Experimental' adds uncertainty.

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?

No guidance on when to use this tool versus alternatives (e.g., 'create_folder' or 'add_doc_to_collection'). No when-not-to-use or context provided.

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