Append to page

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds meaningful context by specifying 'end (or start)' and 'without replacing it', which clarifies the exact behavioral semantics beyond the structured annotations. It does not disclose error handling or permissions, but given the simple scope, this is sufficient.

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 a single, front-loaded sentence that efficiently conveys the core action, scope, and non-destructive nature. No filler or redundancy.

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 is straightforward, with schema covering most parameters and no output schema required. The description provides sufficient context for selection and invocation, though it does not explicitly mention the need for an existing pageId (implied by 'existing page'). Overall, complete for the tool's simplicity.

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?

The schema covers 75% of parameters with descriptions (all except isHtml), so the baseline is near 3. The tool description itself does not add parameter-specific meaning beyond what the schema provides, and it does not compensate for the missing isHtml description.

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 'Add' and specifies it targets an existing page without replacing it, distinguishing it from createPage (new pages) and deletePage. The phrase 'end (or start)' also preemptively covers the append/prepend functionality, making the 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 clear context: use this to add content to an existing page, as opposed to creating a new page. However, it does not explicitly mention alternatives or exclude cases, so it lacks deeper guidance on when not to use it.

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