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

With no annotations, the description carries the full behavioral burden. It reads as a static reference lookup, but it never says whether output is prose, structured rules, or token lists, how large the response is, or whether anything is stateful. Read-only behavior is only implied by the noun-heavy phrasing.

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 that front-loads the topic list and follows with the sub-topic detail; there is no filler. It is slightly crammed, but every clause carries content.

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 one-parameter content lookup with no output schema, the description tells an agent what subject matter comes back by topic, which is adequate. It stops short of describing the form of the returned guidance, leaving a gap for a tool whose whole value is the content it returns.

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 coverage is 0%, but the single parameter is an enum of five self-describing values, which the description expands by listing sub-topics (hue meanings and risks, palette roles, typeface classes, brand personality, logo principles, motion purposes and tokens). The value-to-topic mapping is only positional, so it adds moderate rather than decisive meaning.

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 enumerates the topical content covered (colour, type, branding, logo, motion), which maps cleanly to the enum, but it never states the action — that this returns reference guidance for a requested topic. It also gives no differentiation from nearby siblings like get_design_language, get_accessibility_notes, or get_site_guide, which an agent could easily confuse it with.

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 or when-not-to-use guidance, no mention of alternatives, and no indication of what an agent should reach for instead when it wants design-language tokens versus conceptual guidance. Usage is only implied by the topic list.

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