append_blocks_to_page

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that appending occurs at the page end and that blocks_json is a JSON array, but says nothing about permissions, whether existing content is affected, or what the response contains.

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 short sentences with zero filler; the operation is stated first and the parameter hint follows. Nothing is redundant or buried.

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?

An output schema exists, so return values need no explanation. However, for a tool whose whole payload is an untyped JSON string at 0% schema coverage, the definition leaves the block object shape and page_id semantics entirely unspecified, which is a meaningful gap for correct invocation.

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%, so the schema gives only bare types (two strings). The description partially compensates by saying blocks_json is a JSON array of block objects, which clarifies the encoding of a string-typed parameter, but page_id and the structure of the block objects remain undocumented.

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?

States a specific verb (append) and resource (blocks to a page) plus the positional constraint (end of a page), which meaningfully separates it from insert_blocks_after. It does not explicitly name the sibling alternative, but the wording makes the distinction inferable.

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?

"Append ... to the end of a page" implies the usage context and implicitly excludes positional insertion, but there is no explicit when-to-use/when-not statement and no mention of when to prefer insert_blocks_after or insert_table_row. Guidance is implied rather than stated.

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