bricks_get_page

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It states it returns the full element tree with settings, styles, and content, but omits side effects, permissions, limitations, or whether it is read-only. This is insufficient for a tool with zero annotation context.

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 composed of three focused sentences with no fluff. It front-loads the main purpose, then expands on return content, and ends with a usage hint. Efficient and well-structured.

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 exists, so the description must clarify the return value. It states 'Returns the full element tree' which is helpful, but lacks detail on the summary parameter's effect, potential size limitations, or the structure of the JSON. Adequate but incomplete for a tool with three parameters and complex output.

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 coverage is 100%, so the description adds little beyond schema descriptions. It provides a usage hint for content_area that is already present in the schema. No additional parameter context beyond what the schema already conveys.

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 it gets the complete Bricks Builder JSON data for a specific page, with specific verb ('Get') and resource ('page'). It distinguishes from siblings by mentioning alternative use of content_area for header/footer, but does not differentiate from other page-specific get tools like get_page_assets or get_page_schema.

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 a hint about using content_area for header/footer data, implying when to use this tool differently. However, it offers no explicit 'when to use' vs 'when not to use' guidance, and does not reference alternative sibling tools for specific tasks (e.g., get_page_assets for assets, get_page_seo for SEO).

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