AppFlowy Cloud MCP Server

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

No annotations provided, so description must carry full burden. It fails to disclose whether this invalidates the old token, what error conditions to expect, or the format of the response (new token pair vs. access token only).

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 single sentence with no redundancy. However, the brevity comes at the cost of necessary explanatory detail, making it under-specified rather than efficiently concise.

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 zero schema descriptions, no annotations, and no output schema, the description should explain the token flow, parameter details, and return values. It provides none of this, leaving critical gaps for proper agent operation.

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 inadequately compensates. While it mentions 'refresh token,' it does not describe the parameter's format, source (from login response), or the required 'request' wrapper object structure.

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 specific action (refresh) and target (access token) but is somewhat tautological ('using refresh token'). Does not distinguish from sibling tool 'appflowy_login' or clarify the OAuth flow context.

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 (e.g., when access token expires) versus the login tool, nor does it mention prerequisites like obtaining the refresh token from a previous authentication.

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