Retrieve theming documentation covering theme authoring and override patterns for a token-driven SCSS design system, so you can define and customize themes without guessing syntax.
Return THEMING.md — theme authoring + override patterns.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the burden. It reveals the operation is a read-only lookup of a named document, which is informative, but doesn't state whether content is static, cached, or its size/scope limits. Minimal but accurate disclosure.
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?
Single short sentence, front-loaded with the target document and scoped to its content. No waste.
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-param document reader with no output schema, the description sufficiently states what is returned. It could route better among the ~30 sibling tools, but the tool itself is fully described.
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?
Zero parameters, so baseline is 4. Nothing to explain and no schema gap to compensate for.
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 (Return) and resource (THEMING.md) and describes its content scope (theme authoring + override patterns). It's clear what it does, though it doesn't explicitly differentiate from sibling read_* tools like read_readme beyond the filename itself.
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?
Implied usage: fetch this doc when you need theme authoring/override info. No explicit when-to-use vs alternatives (e.g., get_theme or list_themes). Adequate but thin given the many sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.