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 the full burden of behavioral disclosure. It fails to mention whether results are paginated, the format of returned row IDs, error conditions, or confirmation that this is a read-only operation (though implied by 'List').

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 single sentence with no redundancy. However, it may be overly terse given the lack of supporting metadata (annotations/output schema), leaving significant informational gaps that could have been addressed with additional structured sentences.

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 output schema, and no annotations, the description is insufficient. It omits parameter semantics, return value structure, and behavioral constraints that are necessary for correct invocation when structured metadata is absent.

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?

With 0% schema description coverage for the two required parameters, the description must compensate but fails to mention 'workspace_id' or 'database_id' at all. While the parameter names are somewhat self-descriptive, the description adds no semantic context about valid formats or where to obtain these values.

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?

States a specific verb (List) and resource (row IDs in a database), clearly distinguishing from sibling 'get_row_details' by specifying it returns only IDs rather than full details. However, it doesn't explicitly differentiate from 'list_databases' or 'list_workspaces' beyond the resource name.

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?

Provides no guidance on when to use this tool versus alternatives like 'get_row_details' or the prerequisite workflow (e.g., obtaining workspace_id/database_id from list_workspaces/list_databases). No 'when-not-to-use' or conditions are specified.

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