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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, and the description stays consistent with them ('opens nothing by itself'). It adds useful behavior beyond the annotations by saying the return value is procedural guidance with screens, buttons and fields. The closing note about AppFlowy's official REST API and the lack of a hosted MCP server is background justification rather than behavior the caller needs, so it adds little operational value.

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 key point (does not perform the action; returns instructions) is stated early, which is good, but the definition is padded with an API-availability aside dated 25 Oct 2026 that does not help an agent decide or call correctly. The middle sentence packs workflow routing and negated behavior together, making it slightly denser than necessary.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so ('how to do it in AppFlowy step by step (screens, buttons, fields)'). Combined with the explicit next-step routing to the browser tools, an agent has enough to invoke it and act on the result; only the relationship to the neighboring share/create page tools is left unstated.

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 takes zero parameters and the schema is empty, so there is no parameter meaning to add; the baseline of 4 applies. The description correctly implies no inputs are required, since the page context must come from elsewhere in the session.

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 names a specific verb and resource ('Publish page in the user's own AppFlowy account') and then clarifies the actual effect: it returns step-by-step instructions and 'opens nothing by itself'. That clarification is essential, because the tool name alone would suggest an action. It does not distinguish itself from the similarly named sibling appflowy_share_page, which is the main clarity gap.

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?

It gives a concrete follow-on path ('then do it with the cotlet_browser_* tools in the user's AppFlowy Cloud Browser'), which tells the agent this is a first step in a two-part workflow. However, it never says when to prefer this over appflowy_share_page or when this tool is unnecessary, so the guidance is implied rather than explicit.

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