appflowy_append_blocks_to_page

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

No annotations are provided, so the description must carry the full burden. It only says 'append to the end of a page,' but does not disclose whether the operation is destructive, what happens to existing content, authentication needs, or other behavioral traits.

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?

While the description is brief (one sentence), it is under-specified for a tool with nested parameters. It sacrifices necessary detail for brevity, leaving the agent without crucial information.

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 complexity of the input schema (nested object, array of arbitrary objects), no output schema, and no annotations, the description is wholly inadequate. It fails to specify return values, error handling, block format, or how to use the tool effectively.

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 input schema has 0% description coverage, and the description does not explain any parameter. workspace_id and page_id may be self-explanatory, but the core parameter 'request.blocks' (an array of objects) is left completely undefined; the agent has no idea what constitutes a 'raw AppFlowy document block'.

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 appends raw AppFlowy document blocks to the end of a page. The verb 'append' and resource 'blocks' are specific, and it distinguishes from sibling tools that append markdown, text, or other content (e.g., appflowy_append_markdown_to_page).

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 provides no guidance on when to use this tool versus the several other append tools (e.g., markdown, text, page content). It does not mention prerequisites, limitations, or alternatives.

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