update_page

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

No annotations are provided, so the description must fully disclose behavior. It explains that only non-default fields are sent, how archiving toggles work, and that omitting title/icon_emoji or passing empty strings leaves them unchanged. This covers key behavioral traits, though it could mention idempotency or error conditions.

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 generally concise and front-loaded with purpose. However, the parenthetical note about the implementation's sentinel value is a bit too technical for an agent and could be streamlined.

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 description covers all parameters and behaviors for a mutation tool. An output schema exists (not shown), so return values are covered. However, it lacks mention of permissions, idempotency, or error handling, which would be helpful given no annotations.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning: page_id (implied), title (omit or pass "" to leave unchanged), icon_emoji (same), archived (default False but controls toggle), and properties_json (with concrete examples). This adds significant value beyond the schema's type/default info.

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 'Update' and the resource 'page', and lists specific fields (title, icon, archive status, properties). It distinguishes from sibling tools like update_block_text (which updates blocks) and create_page (which creates new pages).

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 explicit guidance on non-default value sending, archiving toggle behavior, and properties usage with examples. However, it does not explicitly state when to use this tool versus alternatives like move_page or update_block_text.

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