AppFlowy Cloud MCP Server

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

With no annotations provided, the description carries full burden but omits critical behavioral details: how row identity is determined for updates (no row_id in schema), whether updates are partial or full replacements, concurrency handling for pre_hash, and what constitutes existence checking.

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 single sentence wastes no words, but extreme brevity becomes under-specification. No front-loaded constraints or critical warnings about the identification mechanism that would prevent misuse.

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?

Inadequate for a complex mutation operation with nested objects and zero schema documentation. Missing: row identification logic, return value description, error conditions (e.g., conflicts), and field update semantics. The gap regarding how the tool identifies 'existing' rows is particularly critical.

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 0% and the description fails to compensate. No explanation of the 'pre_hash' parameter (likely for optimistic locking), the structure expected within 'cells', the distinction between 'document' and 'cells', or how the target row is identified without a row_id parameter.

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 defines the upsert pattern (update or create) and identifies the resource (row). However, it fails to explicitly distinguish when to use this versus the sibling 'appflowy_create_row' tool, leaving ambiguity about selection criteria despite the functional overlap.

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 provided on when to prefer this tool over 'appflowy_create_row' or other alternatives. No mention of prerequisites, idempotency guarantees, or preconditions for the update path versus create path.

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