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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is largely covered. The description does add real value beyond them by clarifying the tool 'opens nothing by itself' and returns procedural instructions instead of acting. The closing note about AppFlowy Cloud's REST API and absence of a hosted MCP server explains why browser tools are needed, but that is background rationale rather than behavior the agent must act on.

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 core behavior and the hand-off to browser tools are front-loaded, which is good. But the final sentence about AppFlowy's REST API surface and the 'checked 25 Oct 2026' verification date is justification clutter rather than something an agent needs to select or call the tool. The middle clause is also a dense run-on.

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?

It states what comes back ('how to do it ... step by step (screens, buttons, fields)') and what to do next, which is adequate for a zero-parameter tool with no output schema. The notable gap is that with no parameters at all, the description never explains how the target page is identified — presumably from conversation context — leaving the agent unsure what scope the returned steps apply to.

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 zero parameters there is no parameter meaning to convey, so the baseline of 4 applies. Schema coverage is 100% and there is nothing the description could usefully add.

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 and then corrects the natural reading of the name by stating it 'Returns how to do it in AppFlowy step by step ... and opens nothing by itself', so an agent learns it is an instruction-producing tool rather than the mutation the name implies. The upfront 'Share page in the user's own AppFlowy account' phrasing is momentarily misleading, but is resolved in the same breath. It does not name any sibling it is distinct from.

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 an explicit follow-on workflow: call this, then perform the steps 'with the cotlet_browser_* tools in the user's AppFlowy Cloud Browser'. That is genuine sequencing guidance. However, it never says when this is preferable to appflowy_publish_page (a plausible alternative for making a page visible) or to cotlet_app_guide, and offers no exclusions or preconditions.

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