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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, idempotentHint=true), so the burden is lower. The description still adds real value by disclosing the two response shapes — an overview without a topic versus the full rule with wrong/right code examples with one — which is precisely the output-varying behavior an agent needs to know and could not derive from annotations.

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?

Front-loaded with 'Start here,' then two tight clauses mapping the no-topic and with-topic paths. Every sentence earns its place with zero filler, and the branch structure mirrors the single optional parameter.

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 single-optional-parameter, read-only docs tool with no output schema, the description fully specifies both invocation modes and what each returns. Nothing an agent needs to call it correctly is missing.

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 100% and the enum is described, so the baseline is 3, but the description goes further by explaining the semantic effect of supplying the topic parameter versus omitting it. It does not explain that only the listed topic values are valid, though the schema covers 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 communicates a specific resource (the nuvui rules/guidance) and frames itself as the entry point with 'Start here.' However, it never states an explicit retrieval verb, so the agent must infer that calling this returns documentation content. It is clearly distinguishable from get_block/get_tokens/list_components, but the differentiation comes from the 'start here' framing rather than an explicit scope statement.

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?

Strong conditional guidance: 'Without a topic' vs 'With a topic' tells the agent exactly what each invocation mode returns, and 'Start here' signals this is the first tool to call. It stops short of naming alternatives or when-not-to-use conditions (e.g., whether to prefer list_guides or list_components for specific lookups).

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