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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered. The description adds useful content-level context (that the payload includes brand restyling guidance and a cn() config, not just raw tokens), but says nothing about return shape or size 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 sentence listing four substantive payload areas with no filler. Content is front-loaded on the most commonly needed item (colour tokens) and every clause 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?

For a no-arg read tool with no output schema, the description usefully previews the returned subject matter, which is the main thing an agent needs to decide to call it. The one gap is that it never indicates the format or rough structure of the response, so an agent cannot anticipate how the theme data will be shaped.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies for a no-parameter tool whose schema is trivially complete.

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 enumerates the specific contents of the Liro theme resource: colour tokens with light/dark values and their roles, brand restyling via CSS overrides, the type scale, and the cn() config. That is concrete and resource-specific, but it is written as a noun phrase with no verb ('Returns...'), and it never distinguishes itself from siblings such as get_component or get_installation.

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?

Usage is only implied: an agent can infer this is the tool for theming, colour, and typography questions. There is no explicit when-to-use statement, no prerequisite, and no mention of when an agent should prefer get_component_code or get_recipe instead.

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