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

With no annotations, the description carries the full burden, and it does disclose the breadth of the return payload ('every token... light and dark, plus its design principles'), which is genuinely useful scope information. It says nothing about permissions, read-only nature, response size, or caching, but for a read-only 'get' verb the disclosed content scope partially compensates.

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 dense sentence with zero filler, front-loading the resource and the payload scope. Nothing in it is redundant with the name or 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?

No output schema, no annotations, and 0% parameter coverage mean the description must do the work, yet it never explains the id enum or routes the agent to find_noodles/list_noodles for valid ids. For a tool with a 59-value opaque enum this leaves a significant gap.

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 required parameter 'id' is an unlabeled enum of 59 opaque codenames (mian, ramen, udon, pho...). The description adds no meaning to this parameter, not even clarifying that the id selects a design system or pointing to how valid values are discovered.

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 decodes the opaque codename 'noodle' by stating it returns every token of a design system (light and dark) plus design principles, so an agent knows what the payload contains even though the name alone is meaningless. However, it offers no differentiation from closely named siblings such as get_noodle_css, list_noodles, or find_noodles.

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 statement of when to use this tool versus list_noodles, find_noodles, or get_noodle_css. The agent must infer from the name and description alone that this is the single-system fetch, and no prerequisites or exclusions are given.

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