Read Tailwind theme

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds that custom theme values are included alongside standard tokens, which is useful context, but it says nothing about behavior when no Tailwind config is found, whether defaults are merged in, or how limit/offset pagination behaves.

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?

Two short sentences, the read scope front-loaded and the one piece of operational advice placed second. No filler or restatement of the title.

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, the description is responsible for framing the return value, and it does list the token categories. However, it omits pagination behavior for limit/offset, result ordering, and failure modes, leaving gaps for a tool whose output shape is otherwise undocumented.

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% with five fully documented parameters, so the schema carries the load and 3 is the baseline. The description's mention of colors/spacing/breakpoints loosely maps to the namespace parameter, but adds no syntax or semantics beyond the schema.

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 (Read) and resource (the project's design tokens), enumerating what's returned: colors, spacing, breakpoints, fonts, custom values. It distinguishes itself from siblings like tailwind_contrast or tailwind_migrate by resource, but never explicitly contrasts with tailwind_search_classes or tailwind_variants, so sibling differentiation is left implicit.

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?

The only guidance is "Use the project's own token names instead of generic ones," which is a naming convention, not a when-to-use rule. There is no statement of when to prefer this over tailwind_search_classes or tailwind_variants, and no prerequisites or exclusions.

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