Update Page Section

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

Annotations already mark destructiveHint=true, and the description adds valuable behavioral context by explaining that only the section under the named heading is replaced while macros, layouts, and other sections remain intact. This clarifies the scope of the destructive operation beyond the annotation alone.

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 concise and front-loaded, with the core behavior stated in the first sentence. The second sentence adds valuable behavioral detail and rationale without unnecessary repetition or 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?

Given the high schema coverage, output schema, and destructive annotation, the description is largely complete. It explains what is and is not affected, provides rationale, and the parameter descriptions handle edge cases like case-sensitive heading text and content format. Minor gaps such as duplicate heading behavior are not addressed but are not critical.

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 the parameters are already well-documented. The tool description reinforces that only body content is replaced and heading matching is exact, but most parameter-level meaning is appropriately handled by the input schema. This meets the baseline for fully covered 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 a specific verb and resource: 'Update a single section of a Confluence page' and clarifies exactly what is replaced. It clearly distinguishes itself from a full-page update by emphasizing that only the content beneath a named heading changes.

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 clearly identifies when to use this tool—updating one section without affecting the rest—and contrasts it with the riskier full-page Markdown round-trip workflow. It does not explicitly name the alternative tool, but the usage context is clear from the description and sibling list.

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