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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses meaningful behavior: a five-minute live-catalogue cache and a bundled-snapshot fallback marked with origin and fallbackReason. That fallback/origin disclosure is genuinely useful and not derivable from the annotations. The sentence about 'content provenance is separate from origin when returned by the implementation brief' is muddy and undercuts it slightly.

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?

Purpose is front-loaded, which is good, but the full JSON return shape is restated at length even though an output schema exists (redundant), and the provenance sentence is confusing filler. Several lines do not earn their place against the structured fields.

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?

Covers purpose, arg example, fallback/caching behavior, and error handling; with an output schema present it need not explain return values (though it does, redundantly). It is largely complete for a single-parameter read tool, missing only explicit sibling routing.

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 description coverage is 100% and the single slug parameter is already documented in the schema, so the baseline is 3. The description adds only extra example values ('glassmorphism', 'neo-brutalist') beyond the schema's example, which is marginal added meaning.

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+resource ('Get one style's full profile') and enumerates the exact fields returned (philosophy, palette, do/don't rules, keywords, availability flags). An agent can distinguish this from siblings like stylekit_get_style_tokens and stylekit_get_component_recipe because it describes the aggregate profile rather than the individual artifact.

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?

Provides a usage example ('how should I use neo-brutalist?' -> slug) and notes the error behavior for unknown slugs, which implies when to call it. However it never states when to use this versus stylekit_search_styles (to discover a slug) or the token/recipe/shadcn siblings, leaving the routing to inference.

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