bricks_update_page_settings

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

No annotations provided, so description carries full burden. It says 'Update' (mutation) but does not disclose destructive potential, permission requirements, or behavior of the merge parameter. No return value description.

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?

Single, front-loaded sentence that states action and examples. No unnecessary words. Efficient for quick scanning.

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?

No output schema, no annotations, and limited behavioral context. The description covers what to update but misses prerequisites (e.g., page_id needed), return format, or side effects. Adequate for a simple tool but not fully 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 covers 100% of parameters with descriptions. The description adds value by listing example fields for the settings object (metaRobots, header/footer template, per-page overrides), which gives context beyond the schema's generic 'Settings to update'.

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?

Description states it updates page-level settings and gives concrete examples (metaRobots, header/footer template, per-page overrides). It clearly distinguishes from sibling like bricks_update_page (full page update) and bricks_update_page_seo (SEO-specific), though not explicitly.

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?

No guidance on when to use this tool versus alternatives. Does not mention scenarios or exclusions. The description implies use for settings, but doesn't clarify differences from other update tools.

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