bricks_get_global_css

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

No annotations provided, so the description must fully disclose behavioral traits. It only says 'Get' implying read-only, but fails to mention return format, potential performance impact, or any prerequisites. The description carries insufficient transparency for a tool with no annotation support.

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?

A single, front-loaded sentence with no extraneous words. Every word is necessary, and the information is immediately accessible.

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?

For a zero-parameter, no-output-schema tool, the description is minimal. It doesn't mention return format (e.g., raw CSS string, JSON), which could affect tool invocation. While simple, it leaves some ambiguity about what the agent receives.

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?

Zero parameters; baseline is 4. The description adds nothing beyond the empty schema, but as there are no parameters to document, it meets the baseline without loss.

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 gets global custom CSS from Bricks Builder settings. It uses a specific verb 'Get' and resource 'global custom CSS', and is distinct from sibling tools like bricks_update_global_css (update) and bricks_get_settings (general settings).

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 explicit guidance on when to use this tool vs alternatives like bricks_get_theme_styles or bricks_get_css_variables. The zero-parameter simplicity implies straightforward usage, but differentiation from similar read tools is lacking.

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