bricks_get_page_elements

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

With no annotations provided, the description carries the full burden. It states the tool returns 'all elements' but does not clarify whether this includes nested or hidden elements, or if there are performance implications for large pages. Basic read behavior is implied but not elaborated.

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 only two sentences, with no filler or redundant information. Every word adds value, front-loading the core action and return type.

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 tool has no output schema and no annotations, so the description should provide more context about the return value structure or limitations. It mentions 'structured JSON' and 'all elements', which is functional but minimal. Sibling tools like 'bricks_get_element_tree' are not mentioned, so completeness is only moderate.

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 100% (all three parameters have descriptions). The description adds minimal extra meaning—'by ID' and 'page/post' are already in the schema. No additional format or usage examples are given, so baseline 3 is appropriate.

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 'Get' and the resource 'Bricks elements array for a page/post', making the tool's action unambiguous. It distinguishes itself from siblings like 'bricks_add_element' by focusing on retrieval, and explicitly mentions returning 'structured JSON'.

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 is provided on when to use this tool versus alternatives such as 'bricks_get_element_tree' or 'bricks_set_page_elements'. The description implies usage for retrieving elements but offers no exclusions or context about optimal scenarios.

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