get_widget_css_styling_guide

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

Beyond the readOnly/idempotent annotations, it discloses that the response is the same SYSTEM_PROMPT used server-side, that agentId causes the agent's current customCSS to be appended, and what to do with the result. That is behavior the annotations cannot convey.

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 critical instruction ('MUST CALL FIRST') is front-loaded and the closing sentence defines the workflow. The parenthetical (a)-(f) enumeration is dense and longer than strictly necessary, but each item corresponds to guide content the agent will receive, so nearly every phrase earns its place.

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, yet the description enumerates exactly what the return contains and how agentId modifies it, and it names the follow-up persistence tool. An agent has everything needed to call it and act on the result.

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% and the schema already describes agentId; the description reinforces its purpose (append existing customCSS so rules are extended rather than duplicated), which is the key semantic nuance. No further syntax detail is needed for a single optional string.

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?

States a specific verb (get) and resource (widget CSS styling guide) plus the exact scope it covers, listing the guide's sections (a)-(f). The trigger examples and the explicit mention of Convocore/vg widget make it impossible to confuse with sibling tools like get_agent_custom_css or update_agent_custom_css.

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?

Opens with an explicit 'MUST CALL FIRST whenever...' condition, gives five concrete trigger phrases, and closes with the downstream step: generate CSS following the guide, then call update_agent_custom_css. Both when-to-use and the sequence relative to a sibling are spelled out.

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