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

Annotations already declare readOnly/destructive=false/openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: the kit is cheap to read, and edits to the kit propagate everywhere, which explains the downstream consequence of using tokens. It also describes the payload (colors, fonts, type scale, token ids) despite there being no output schema.

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 dense sentence that front-loads what is returned, then the imperative guidance and inline examples. No filler 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 and a single trivial parameter, the description carries the return-value burden well by naming the kit contents and the token reference format. An agent has everything needed to call it correctly and use 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?

Only one parameter (site_id) and schema coverage is 100%, so the schema fully documents it, including its provenance ('from list_wordpress_sites'). The description adds no further parameter detail, which is the expected baseline when the schema does the work.

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) plus the exact resource (the site's Global Brand Kit) and enumerates what it contains: colors, fonts, type scale, and referenceable token ids. The agent can immediately distinguish this from sibling getters like get_brand_profile or wp_style_keys.

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?

Gives an explicit timing directive — 'Call this BEFORE styling pages' — and names the downstream consumers (wp_create_page/wp_update_page styles) with concrete syntax examples. It lacks an explicit when-not or a routing comparison against the closest sibling (wp_style_keys), so it stops short of a 5.

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