appflowy_append_blocks_to_page

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

With no annotations, description fails to disclose behavioral traits such as error handling, authorization needs, or effects of invalid blocks. Only states action without side-effect 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?

Excessively brief—single sentence lacking necessary detail. Conciseness should not sacrifice critical information; here it omits parameter explanations and usage context.

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 3 required params, nested object, no output schema, and no annotations, description is completely inadequate. No mention of block format, error conditions, or return behavior.

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 has 0% description coverage; description does not explain any parameter meanings. Complex nested object 'request' with 'blocks' is entirely undocumented, leaving the agent without structural guidance.

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?

Description clearly states verb 'append', resource 'raw AppFlowy document blocks', and location 'end of a page'. It distinguishes from sibling 'appflowy_append_text_to_page' by specifying blocks vs text.

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?

No guidance on when to use this tool versus alternatives like appflowy_append_text_to_page. Missing context about prerequisites or ideal scenarios.

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