generate_system

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

No annotations are provided, so the description must reveal behavioral traits. It mentions writing files (implied by dryRun) but does not state whether it overwrites existing files, any side effects, or required permissions. This is insufficient for a tool that generates and writes files.

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 concise sentences with no redundancy. The purpose is front-loaded in the first sentence, and the second provides a key usage tip. Every word adds value.

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?

Despite having no output schema, the description does not explain what the tool returns (e.g., list of generated files, preview output). With many sibling tools, it lacks guidance on when to choose this over others, and crucial details about file overwriting behavior are omitted.

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%, so baseline is 3. The description adds value by showing examples of template values and recommending dryRun usage, but does not elaborate on the JSON format for params beyond the schema.

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 explicitly states 'Generate a new design-token system from a template' and lists supported types (color palettes, spacing scales, full systems), clearly distinguishing it from sibling tools like generate_palette or generate_scale which are more specific.

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 provides a useful tip ('Use dryRun=true to preview first') but does not explain when to use this tool versus alternatives like generate_palette or generate_scale, nor does it mention cases where this tool should not be used.

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