sb_page_update

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

Annotations already declare this is a non-read, non-destructive mutation, so the safety profile is covered. The description adds genuinely non-obvious behavior: it reads the page first and merges settings key by key so unnamed keys survive. It omits mention of dry_run and any auth/permission requirements, keeping it below a 5.

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?

Three dense but front-loaded sentences with no filler; the editable-fields list and the merge caveat come first, with template semantics last. Slightly packed, but every sentence carries load.

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 12-parameter tool with a nested SEO object, no output schema, and low schema coverage, the description covers most meaningful parameters and the key merge behavior. Gaps remain around dry_run and site_id, but an agent has enough to call it correctly.

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 only 17%, so the description must compensate, and it largely does: it explains seo is merged key by key, and clarifies render_for (move entities onto this page) vs render_default (return to type default) and default_template. Only page_id, site_id, and dry_run are left without added meaning.

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?

States a specific verb ('Edit') and resource ('a page'), then enumerates exactly which fields are editable (name, slug, home flag, order, SEO, members_only). The template-page sentence further narrows the scope to a distinct behavior class, making it clearly distinguishable from siblings like sb_page_create and sb_page_repair.

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?

Provides clear context for when the template-specific parameters apply (on a template page such as product, category, post) and what default_template/render_for/render_default accomplish. It does not explicitly name an alternative tool or state exclusions, so it falls short of full when/when-not routing.

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