Update page

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, providing a baseline. The description adds which aspects can be updated but does not disclose side effects, permission requirements, or nuances of setting trash/lock state.

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?

A single, front-loaded sentence that efficiently lists all key update dimensions with no extraneous content.

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?

For a tool with 6 parameters and nested objects, this description is minimal. It lacks parameter structure details, usage prerequisites, and behavior nuances. Although an output schema exists, the description does not sufficiently compensate for the low schema coverage.

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. It maps 'properties', 'icon', 'cover', 'lock state', and 'trash state' to the parameters, but it does not explain the required pageId, nor the structure of icon/cover/properties objects.

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 updates page-related entities (properties, icon, cover, lock state, trash state) using the specific verb 'Update', distinguishing it from sibling tools like create_page, get_page, and update_block.

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 intended use for updating a page is implied by the name and description, but there is no explicit guidance on when to use this tool over alternatives like update_block, nor any mention of exclusions or prerequisites.

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