update-page-content

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

The description discloses important behavioral nuances beyond the idempotentHint annotation: it states that if no body/title/editingRoles is provided, nothing is written and guidance is returned, and that showStyleguidePreview can inline the styleguide. This adds value beyond the annotation, though it doesn't detail permissions or return structure.

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 sentences, front-loaded with the primary purpose, followed by a conditional behavior note and an explicit alternative. Every word earns its place with no fluff or repetition.

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 tool has 7 parameters, no output schema, and moderate complexity, the description covers the core behavior, the no-op case, and the alternative tool. It doesn't explain what the returned 'guidance' looks like or the exact effect of partial parameters, but for an update/create operation this is reasonably complete.

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 coverage is 100%, so the baseline is 3. The description adds some meaning by tying body/title/editingRoles together as the set triggering no-op behavior, but it doesn't provide significantly more than the schema already does. It does not fully compensate for the lack of parameter examples or additional context.

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 tool's function: 'Update or create a page with new content, replacing the entire body.' This uses a specific verb and resource, and distinguishes it from the sibling patch-page-content by noting it replaces the entire body rather than making targeted edits.

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?

Explicit guidance is provided: 'For targeted edits to existing content, use patch-page-content instead.' This gives a clear alternative and also explains the conditional behavior when no body/title/editingRoles are provided, offering both when-to-use and when-not-to-use direction.

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