Append Blocks

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

No annotations provided, so description must disclose all behavioral traits. Only mentions insertion position (end or after block). Missing details like idempotency, error conditions, limits, or what 'simplified blocks' entails.

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?

Two concise sentences front-load core action and optional behavior. No redundant or extraneous text.

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?

Describes main insertion behavior but lacks explanation of 'simplified blocks', markdown conversion, or return values (no output schema). Missing details that could help agent understand tool's scope vs siblings like markdown_to_blocks.

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 covers all parameters with descriptions. Description adds context: after_block_id inserts after a specific direct child. This clarifies usage beyond schema, compensating for 100% schema coverage (baseline 3).

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?

Verb 'append' clearly states action; 'blocks or Markdown to a page' identifies resource. Not explicitly contrasted with siblings like replace_page_content or update_block_text, but use of 'append' and optional after_block_id provides differentiation.

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?

Describes default behavior (insert at end) and optional parameter usage. No guidance on when to use this tool versus other block manipulation tools, nor prerequisites or restrictions.

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