Check AppFlowy auth

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 does state 'Read-only,' which is a key safety trait, but it omits details about failure behavior, response format, or any side effects beyond the read-only claim. The description is not contradictory to annotations, but it is thin on behavioral context.

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?

Two sentences with zero waste. The core purpose is front-loaded, and the read-only qualifier is placed immediately after the action. Every word earns its place.

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?

The tool is simple (no params, no output schema), but the description does not state what the tool returns (e.g., success/failure, error details). Since there is no output schema to fill that gap, an agent cannot know what to expect from a call. The description covers the action but leaves the outcome ambiguous.

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?

The tool has zero parameters, so there is nothing to explain. The schema coverage is trivially 100%, and the description does not need to elaborate on parameters. Baseline of 4 applies per the rubric for tools with no parameters.

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 a specific action ('Verify') and a specific resource ('the configured account can log in to AppFlowy and reach it'), clearly distinguishing it from sibling tools that list or search pages. It also explicitly marks it as read-only, reinforcing its distinct role as an authentication check.

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?

The description implies a use case—checking auth before other operations—but does not explicitly state when to use this tool versus alternatives or mention prerequisites or exclusions. An agent would infer it is a prerequisite check, but the guidance is not spelled out.

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