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 responsibility for behavioral disclosure. It fails to mention what 'with_doc' implies (likely including associated document content), error behavior for missing IDs, or whether this is a read-only operation (implied by 'Get' but 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?

Extremely brief at 7 words. While it wastes no words and uses active voice, it is under-specified for the tool's complexity. However, the single sentence is appropriately structured with the verb front-loaded.

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 4-parameter tool with zero schema documentation and no output schema. The description omits return value structure, the relationship between rows and documents (with_doc), and hierarchical context (workspace/database). Needs significant expansion to be usable.

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, the description must compensate by explaining all 4 parameters. It only implicitly references row_ids via 'IDs'. It fails to explain: workspace_id/database_id (hierarchy/context), row_ids format (comma-separated? JSON array?), or with_doc behavior. Critical gap given the schema lacks descriptions.

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 the basic action ('Get details') and resource ('rows'), and includes 'by IDs' which helps distinguish from the sibling appflowy_list_rows. However, 'details' is vague (what fields are returned?) and it doesn't clarify the AppFlowy-specific context (databases, workspaces).

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 versus list_rows (filtering vs. specific ID lookup) or prerequisites (e.g., that workspace_id and database_id must be obtained from list_workspaces/list_databases first). No mention of error handling for invalid IDs.

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