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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one genuine behavioral trait — that omitting `topic` switches the call into a topic-listing mode — but says nothing about output format, whether topics must match the listed categories, or failure behavior for unknown topics.

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 the content scope front-loaded and the parameter hint trailing. Efficient, though the enumerated topic list reads slightly like a payload dump rather than a purpose statement.

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 exists, yet the description covers what kinds of documents come back at a high level. For a one-optional-param read tool that is barely enough; topic validity and return format remain unspecified, and siblings are not disambiguated.

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% and the single `topic` param has no description, so the description must compensate. It does partially, by explaining the omit-to-list behavior, but it never states valid topic values, casing, or format despite enumerating plausible topic names in prose.

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 what the tool returns — the design rules behind the components (colour roles, layout/density, architecture, brand rules, README spec) — which tells an agent this is the foundations/documentation resource. However, it never names or contrasts with siblings like get_component or get_setup, so the agent must infer the split from names alone.

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?

Aside from a parameter-behavior note ('Omit `topic` to list topics'), there is no statement of when to reach for this tool instead of get_component, get_setup, or list_tokens. The implied use case (fetch design foundation docs) is left for the agent to infer.

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