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

Annotations already disclose readOnly=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds useful behavior beyond those hints: the guideline is stored verbatim, rendered in the Brand Kit tab and downloadable HTML doc, and does not touch any live site. It does not detail overwrite semantics for an existing kit or permission requirements.

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 opening purpose and routing are front-loaded before the long brand_kit field enumeration. The density is high and could be more bullet-like, but the length is largely justified by the complete-guideline requirement and the empty nested schema.

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 complex write tool with no output schema, the description supplies the missing nested parameter structure, distinguishes the sibling apply-tool, and states the stored/rendered outcome. With annotations covering the safety profile, the combined definition is complete enough to invoke correctly.

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%, but the brand_kit object has empty nested properties, so the description carries most semantic weight. It provides an extensive nested field map (meta, colors, colorMeta, fonts, typography, buttons, etc.) and clarifies that site_id is the BRAND id from list_sites, not a WordPress site id.

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?

Starts with a specific verb and resource: store/replace a complete brand guideline on XeoRank. It names the scope, says it works for any brand/platform, and distinguishes itself from wp_set_brand_kit, so an agent can identify the correct tool without opening the schema.

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?

Explicitly frames this as the 'populate the XeoRank end' path and names the exact alternative, wp_set_brand_kit, for applying the Elementor-writable subset to a connected WordPress site. It also explains when this tool works even when the live site cannot be styled.

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