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 discloses nothing about safety (is it read-only?), side effects, rate limits, or return format. The word 'List' implies read-only, but this is not explicit.

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 is efficiently worded with no redundancy, but given the lack of annotations and schema coverage, this brevity results in under-specification rather than excellent conciseness.

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?

With no output schema, no annotations, and zero parameter documentation in the schema, the description fails to provide necessary context. It should at minimum describe the return structure (list of databases) and parameter 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 has 0% description coverage. While the description mentions 'workspace' implying the workspace_id parameter, it doesn't explain what a workspace_id is, where to obtain it (likely from appflowy_list_workspaces), or its format. Insufficient compensation for the schema deficiency.

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 uses a specific verb ('List') with clear resource ('databases') and scope ('in a workspace'). While it doesn't explicitly differentiate from siblings like appflowy_list_workspaces, the resource distinction is obvious from the tool names.

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 like appflowy_list_workspaces or how it relates to appflowy_get_database_fields. No mention of prerequisites or workflow context (e.g., that you typically need workspace_id from list_workspaces first).

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