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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to state whether this is a destructive operation, if it requires specific permissions, or what the append semantics are (end of page only?). It does not address idempotency or error conditions.

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?

Extremely brief at four words. While efficient without filler, it is arguably underspecified rather than concise; however, the single sentence structure is appropriately front-loaded with the core action.

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?

For a content-modification tool with no output schema or annotations, the description is insufficient. It omits return value details, side effects, block structure specifics, and error handling that would be necessary for confident agent 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 coverage is 100%, documenting 'page_id' and 'blocks' adequately. The description adds no semantic depth beyond the schema (e.g., block object structure, ID format), meriting the baseline score for well-documented schemas.

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 states the basic verb (append) and target (blocks to a page), avoiding complete tautology. However, it fails to differentiate from sibling 'update_page' or clarify what constitutes a 'block' in this context, leaving the scope vague.

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 provided on when to use this tool versus alternatives like 'update_page' or 'create_page'. No mention of prerequisites, positioning (end vs. insertion), or workflow context.

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