bricks_get_page_settings

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

No annotations are provided, so the description carries the full burden. It only says 'Get', implying a read operation, but does not explicitly state that it is non-destructive, idempotent, or any other behavioral traits like permissions or rate limits. The minimal disclosure leaves room for ambiguity.

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 a single sentence of 10 words, front-loaded with the action and resource. It includes key examples without additional fluff, making it highly efficient.

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?

Given the simple input schema (single parameter) and no output schema, the description adequately covers the tool's purpose and the kind of data it retrieves. However, it omits any mention of return format or error conditions, which would be helpful for a complete picture.

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?

The input schema has 100% coverage with a description for page_id ('WordPress page/post ID'). The tool description adds value by listing the types of settings retrieved (metaRobots, custom header/footer, overrides), which provides context beyond the parameter itself.

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 retrieves 'Bricks page-level settings' with specific examples (metaRobots, custom header/footer assignment, per-page overrides). The verb 'Get' and resource are specific, and it distinguishes from sibling tools like bricks_get_page (which likely returns page content) or bricks_get_page_seo (SEO-specific).

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 no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It simply describes the function without helping the agent decide between similar getter tools.

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