bricks_generate_bem_component

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

With no annotations, the description carries the full burden. It discloses the tool is a creation operation that is safe to re-run due to bulk upsert. It does not mention potential side effects like overwriting existing classes, but the 'safe to re-run' note mitigates this. Overall, it provides reasonable behavioral 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 two sentences with a clear front-loaded purpose statement. Every sentence adds necessary information without excess.

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 input schema's nested objects and lack of output schema, the description provides sufficient context with the 'elements' and 'modifiers' explanations and example. The tool's behavior and output (creating CSS classes) are well-covered.

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 baseline is 3. The description adds value by explaining the structure of 'elements' with the '_root' key and providing an example, which goes beyond the schema's basic descriptions.

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 generates a complete BEM component as global CSS classes, creating block, element, and modifier classes in one call. It provides an example and distinguishes from siblings like bricks_apply_bem_component and bricks_validate_bem.

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 mentions 'Uses bulk upsert so it is safe to re-run', which indicates idempotency and a usage scenario. However, it does not explicitly contrast with alternatives like bricks_create_global_class or bricks_apply_bem_component, leaving the agent to infer when to use this tool versus others.

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