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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return content scope ('every token... light and dark, plus its design principles'), which is genuinely useful, but says nothing about permissions, output size, or whether the data is static/cached.

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 tight sentence with zero filler, and the content scope is front-loaded. It is efficient, though its brevity contributes to the surrounding informational gaps rather than being a structural flaw.

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 an opaque enum identifier, no output schema, and no annotations, the description should explain what the id values are and what shape the tokens return. It supplies only a content summary, leaving the caller unable to confidently pick an id or anticipate the response.

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 0% and the single parameter is an opaque 66-value enum (mian, yangchun, linguine...). The description adds no meaning about what these values represent or that they are design-system names, so the agent has no help interpreting the required 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?

The description names the resource content (all tokens of a design system, light and dark, plus design principles) but never states a clear verb or what a 'noodle' actually is, leaving the agent to infer that it fetches a theme/design system by id. It partially differentiates from get_noodle_css and get_design_guide by scope, but the core object remains vaguely defined.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_noodle_css (for CSS), list_noodles, or get_design_guide despite the crowded sibling set. The agent must guess whether this is the right tool for retrieving a design system.

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