append_markdown

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

No annotations are provided, so the description carries the full burden. It does disclose the useful transformation behavior (markdown is converted to Notion blocks) and that appends are additive, but it omits permissions/auth needs, whether appending requires editor access, and error behavior. For an un-annotated mutation tool, this is a significant gap.

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?

Front-loaded one-line purpose and a concise conversion note. The Args/Returns structure is clean, though the Args section only repeats the schema and the Returns note is somewhat redundant given a full output schema exists.

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 output schema covers return values and the description correctly doesn't belabor them. But for a mutation tool with no annotations and no sibling differentiation, the definition is thin — it should state when to use this vs append_blocks and note any permission expectations.

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% and there are 2 required parameters, so the description must compensate. The Args block restates both parameters (page_id, markdown) but adds no format, syntax, or constraint details (e.g., page_id format, markdown dialect/supported syntax). It's the minimum viable restatement.

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 (markdown content to a Notion page), and the conversion detail (markdown to Notion blocks). However, it doesn't distinguish from the sibling 'append_blocks' — an agent must infer the difference between appending markdown vs. blocks, which is exactly the decision point here.

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 when-to-use guidance and no mention of when to prefer append_blocks over append_markdown. The relationship to its closest sibling is left entirely unstated.

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