AppFlowy Cloud MCP Server

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

No annotations are provided, so the description carries full burden. It does not disclose what the 'fields' contain (names, types, constraints?), the return format, or whether this is a read-only operation (though implied by 'Get'). No mention of pagination, rate limits, or error conditions.

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 a single, front-loaded sentence with no redundancy. However, it is arguably under-specified rather than appropriately concise given the lack of schema documentation and annotations.

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 0% schema coverage, no annotations, and no output schema, the description provides insufficient context. For a tool requiring hierarchical identifiers (workspace → database), it should explain the parameter dependencies and what constitutes a 'field' in AppFlowy's data model.

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 0%, so the description must compensate. It mentions 'specific database' which loosely implies the database_id parameter, but completely omits workspace_id. No explanation of parameter formats, valid values, or hierarchical relationship between workspace and database is provided.

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 the basic action ('Get fields') and target ('specific database'), but borders on tautology with the tool name 'appflowy_get_database_fields'. It does not clarify whether 'fields' refers to column schema/definitions or something else, though the sibling tool 'appflowy_list_rows' implies this is metadata rather than data.

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 use this versus sibling tools like 'appflowy_list_databases' or 'appflowy_get_row_details'. Crucially, it fails to mention that users must first call 'appflowy_list_workspaces' and 'appflowy_list_databases' to obtain the required workspace_id and database_id parameters.

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