AppFlowy Cloud MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It compensates partially by describing the return values (access and refresh tokens) since no output schema exists, but it omits critical security context (handling passwords), error scenarios (invalid credentials), and token expiration behavior.

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 consists of two efficient sentences that are front-loaded with the most critical information (action and return values). Every sentence earns its place, though the extreme brevity contributes to gaps in other dimensions like parameter documentation.

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?

For an authentication tool with zero schema descriptions and no output schema, the description is insufficient. It omits security warnings for password handling, workflow context (relationship to refresh_token), and fails to document the required credentials parameters that the schema leaves undescribed.

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 explain the parameters, but it fails entirely. It does not mention that 'email' and 'password' are required within the 'request' object, leaving the agent to infer this solely from the naked schema structure without semantic context.

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 clearly states the action ('Login to AppFlowy Cloud') and the specific outputs ('access token and refresh token'). It implicitly distinguishes itself from the sibling 'appflowy_refresh_token' by specifying that it returns both tokens, suggesting this is the initial acquisition method.

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?

There is no explicit guidance on when to use this tool versus the sibling 'appflowy_refresh_token', nor does it state that this should be invoked before other tools that require authentication. It lacks prerequisites (e.g., valid credentials must exist) and exclusion criteria.

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