appflowy_append_page_content

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions only that content_format defaults to markdown, but omits critical details such as whether the operation is destructive, required permissions, positional behavior (append vs. insert), or error handling. This is insufficient for a general-purpose append tool.

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 is extremely concise, consisting of two short sentences. Every word contributes value—the first sentence defines the purpose and content types, the second adds a default parameter setting. No filler or redundancy.

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 the existence of more specific append tools and a nested parameter without explanation, the description leaves significant gaps. It does not clarify the return value (no output schema), nor does it address error cases or the nature of the appended content. The agent is ill-equipped to use this tool correctly in complex scenarios.

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?

Schema description coverage is 0%, yet the tool description provides no explanation of workspace_id, page_id, or the request object structure. It only notes the content_format default. The agent must infer parameter meanings from names alone, which is inadequate given the nested request object.

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 tool's purpose: appending AI answers, notes, summaries, or generated content to an existing page. It identifies itself as the 'default' tool, which implies a general-purpose role, but it does not differentiate from sibling tools like appflowy_append_markdown_to_page or appflowy_append_text_to_page, leaving ambiguity about when to use this specific tool.

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 its siblings. The term 'default' hints at a broad applicability but fails to specify scenarios or prerequisites. No when-not or alternative tools are mentioned, leaving the agent to guess based on name similarity.

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