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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value by disclosing what the payload contains and, importantly, that it reflects user-tuned overrides rather than defaults – a behavioral distinction no annotation conveys.

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?

One sentence, verb front-loaded, with a compact colon list rather than prose padding. Every clause carries information; only mild criticism is that the field enumeration could be trimmed without losing meaning.

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?

With no output schema, the description must carry return-value information, and it does name the key fields returned. It stops short of describing response shape, empty/unpopulated cases, or behavior when projectId is unknown, but for a one-parameter read tool with full annotation coverage this is close to sufficient.

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% for the single projectId parameter, which already documents that it comes from create-design-system. The description adds nothing about the parameter, so the baseline 3 for fully-documented schemas applies.

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?

States a specific verb and resource ('Returns the design config saved on a generated project') and enumerates the content: color tokens, radius, fonts, icon library, layout density. The 'saved on a generated project' scoping does substantial work separating it from siblings like extract-design-system or get-design-system-kit, though it never names an alternative outright.

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?

Usage is only implied: the phrase 'values the user tuned on the project page' hints this is the read-back counterpart to set-design-config, but there is no explicit when-to-use, no prerequisites, and no named alternative for the case where the caller wants the original (untuned) design system.

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