Append Markdown Content

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

Annotations are all false (readOnlyHint, idempotentHint, destructiveHint). The description adds that it converts Markdown to simple Notion blocks and treats unsupported Markdown as plain text. However, it lacks details on error handling (e.g., invalid block_id), idempotency, or performance. Adequate but not rich.

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?

The description is two well-structured sentences. The first states the core purpose and constraint, the second lists supported elements and provides usage guidance. No wasted words, highly efficient.

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?

The tool has no output schema, but the description does not explain what the tool returns (e.g., success status, appended block ID). Also, the 'format' parameter's purpose (response format) is not mentioned in the description. Missing context on prerequisites and return value leaves the agent underinformed.

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 100%, so baseline is 3. The description adds minimal parameter insight beyond the schema (e.g., noting 'safe subset' for markdown). It does not significantly enhance understanding of the four parameters.

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 verb 'append', resource 'Notion page or block', and specifies a 'safe subset of Markdown' without raw JSON. It explicitly distinguishes from sibling tools for advanced blocks, making purpose unambiguous.

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 explicit guidance: 'Use this when the user provides Markdown-like content and wants it appended; use raw block tools for tables, images...' This clearly indicates when to use and when not, with alternative tools named.

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