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

With no annotations, the description carries the full behavioral burden. It does disclose the output characteristic — up to four matches, each with an explanation — which is real value given there is no output schema. However, it says nothing about whether the call is read-only (it clearly is, but that is left to inference), what happens if both parameters are omitted, or any cost/latency considerations.

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 tight sentences with no filler, and the key scoping information (what drives the recommendation) is front-loaded. The phrase "from a brief in words" is slightly awkward but does not cost the agent comprehension.

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 two-parameter, zero-required read tool with no output schema, the description covers inputs, optionality in practice, and the shape of the result, which is most of what an agent needs. It stops short of explaining behavior when neither input is given and does not clarify how conflicts between brief and URL are resolved.

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%, so both parameters are documented in the schema, establishing a baseline of 3. The description's added value is framing the two as alternatives or combinable ("or both") and echoing the format expectations ("calm editorial, serif"), but it adds no syntax, precedence, or conflict-handling rules beyond that.

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 identifies the resource (a design language / "noodle") and the basis on which one is chosen (a written brief, a site URL, or both), and mentions the return shape (up to four noodles with reasons). The verb "recommend" comes from the name/title rather than the description, but the operation is unambiguous and distinguishable from siblings like list_noodles and 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?

It implicitly tells the agent that a brief, a URL, or both may be supplied, which is useful context, but it never states when this tool is preferable to find_noodles, list_noodles, or get_noodle. No prerequisites, no exclusions, no explicit alternative routing.

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