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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable behavioral context by listing the specific content categories returned (palette variables, spatial scale, modifiers, interactive state, form-confirmation recipe), which helps an agent anticipate the reference material. It stops short of describing the output format or size.

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 sentences with no wasted words. The content categories are front-loaded, and the optional topic parameter is introduced immediately after. Every sentence earns its place.

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 reference-retrieval tool with one optional enum parameter and no output schema, the description provides enough to call it correctly and understand what content it returns. It does not specify the return format, but the enumerated content categories give sufficient context for an agent to decide to invoke it.

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% and the schema already states that 'topic' returns one guide instead of the core reference. The tool description repeats this and provides a few example topics, but adds little beyond the schema’s enum and description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 as a 'Styling reference' and enumerates the content categories (palette variables, styleGuide tokens, spatial scale, etc.), making the purpose clear. It does not explicitly differentiate itself from related sibling tools like suggest_palettes or suggest_font_pairings, but the reference nature is evident.

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?

The description implies usage: call without topic for the core reference, and pass topic for a focused guide. However, it does not state when to choose this tool over alternatives (e.g., suggest_palettes for palette generation) or any exclusions. The guidance is present but minimal.

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