bricks_get_css_variables

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

No annotations are provided, so the description must disclose behavior. It states the return includes variable names and values with examples, but does not mention read-only nature, cost, side effects, or output format. While safe to assume read-only, the lack of explicit behavioral traits reduces clarity.

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 two sentences, each conveying essential information without fluff. It is front-loaded with the core action and resource, followed by a concise list of return value categories. No unnecessary words or repetition.

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?

With no output schema, the description provides examples of returned data (colors, spacing, etc.), which is helpful. However, it lacks details on data structure (e.g., object vs array, key-value pairs) and whether pagination or limits apply. For a simple getter, it is mostly complete but could be more explicit.

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 tool has zero parameters and the schema correctly indicates this. The description adds no parameter information because none exist. Baseline for 0 parameters is 4; the description does not need to compensate.

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 all CSS variables from the Bricks Global Variables Manager, listing example categories (colors, spacing, etc.). It specifies the resource (CSS variables/design tokens) and action (get), distinguishing it from sibling getters like get_global_css or get_color_palette by the source.

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 implies usage for retrieving design tokens but provides no explicit when-to-use or alternatives. Given many sibling get_* tools, the description does not guide selection between this and similar tools like get_color_palette or get_theme_styles, leaving the agent to infer from the name.

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