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

The description adds the critical behavioral detail that the returned standby.design/system URL is the deliverable and must always be provided to the user, which goes beyond the readOnlyHint annotation. It also explains format-specific behaviors (e.g., design-tokens only includes typography & spacing), though some of this is already in the schema.

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?

The description is three sentences and front-loads the core action. The first sentence is dense with the format list, but every sentence carries essential information, including the critical URL deliverable instruction. It could be slightly more concise, but it is not bloated.

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 read-only export tool without an output schema, the description adequately covers the output (code and URL), section filtering behavior, and format semantics. It does not describe error cases or pagination, but the provided information is sufficient for an agent to invoke the tool and handle results correctly.

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%, providing a baseline of 3. The description adds significant value by explaining each format enum value (e.g., 'css' includes semantic shadcn/ui-compatible tokens, 'tailwind' is Tailwind v4 @theme), which is not in the schema's generic 'Output format' description.

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 clearly states the tool generates full token code for a design system URL in one of five explicitly enumerated formats, making the verb and resource specific. It distinguishes from sibling tools (generate_color_palette, generate_type_scale, etc.) by focusing on full-system export rather than individual token types.

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 the usage for full design system export but does not explicitly name alternatives or state when not to use it. Phrases like 'full token code' and 'one format' suggest the use case, but there is no direct comparison to sibling tools or exclusion criteria.

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