append_to_page

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the mutating nature and the return shape, but says nothing about prerequisites (must the page exist?), required permissions, effect on revision history, or whether concurrent appends are safe. For a write tool with zero annotation coverage this is a meaningful 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?

Purpose is front-loaded, and the Args/Returns structure is scannable. The Returns section is somewhat wasted since an output schema already exists, but the whole thing is short and no sentence is egregiously filler.

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-value explanation is redundant rather than missing. What is missing for a mutation tool with no annotations is the operational context: permissions, page-existence behavior, and reversibility. Adequate but with clear gaps.

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 description must compensate, and it largely does: it defines content, id, and path, and adds a genuine precedence rule ("id... preferred when both selectors are supplied") that is absent from the schema. It stops short of format details such as path normalization or empty-content behavior.

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 and resource: "Append Markdown content to a page." The verb "append" inherently distinguishes it from creation siblings like add_page and from edit_page. However, no sibling is named, so the differentiation relies on the agent inferring append-vs-replace semantics on its own.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. The only guidance of any kind is the parameter-level note that "id" is preferred when both selectors are supplied, which is selection between parameters, not between tools.

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