page_update

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

Annotations indicate mutable, non-destructive, idempotent. Description adds that 'data' field uses PATCH merge semantics, while calls without 'data' use PUT full-replace, and explains how to delete keys via page_delete_data. This goes well beyond annotations.

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?

Four sentences: first defines purpose, second states requirements, third suggests alternatives, fourth explains data behavior. Well-structured, front-loaded with essential info, no wasted words.

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?

With 11 parameters and no output schema, the description covers required fields, constraints, alternatives, and data semantics. It could mention validation or side effects for non-data fields, but is largely complete for the tool's complexity.

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 has 0% parameter descriptions. Description adds critical meaning for 'data' (merge vs replace) and explains the requirement that at least one optional field must be supplied. For other fields, it just lists them, but the data behavior is well clarified.

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 'Update arbitrary fields on a page' and lists the specific fields (title, slug, layout_id, etc.), distinguishing from siblings like page_set_hidden and page_set_layout which are mentioned as more explicit for specific fields.

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?

Explicitly states that at least one optional field must be supplied, and recommends using dedicated tools (page_set_hidden, page_set_layout) for updating only hidden or layout_id, providing clear when-to-use guidance.

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