generate_stylesheet

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action without revealing side effects, permissions, whether it modifies the document, or the nature of 'complete'. A generation tool should clarify if it creates new nodes or exports data.

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 a single, front-loaded sentence, which is concise. However, it is too terse and omits important context that would justify its length. Every sentence should earn its place, but this one is insufficient.

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 should explain what the generated stylesheet includes (e.g., colors, typography, spacing). It does not. The tool has two parameters but no clarity on output format or content, making it incomplete for an agent to understand the full behavior.

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%, so the baseline is 3. The description does not add any additional meaning beyond the schema's parameter descriptions (e.g., 'pageId' and 'format' with enum). It could hint at usage, but it does not.

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 action ('Generate') and the resource ('a complete stylesheet from a design file'), distinguishing it from sibling tools like 'create_design_tokens' or 'export_css'. However, it lacks specificity about what 'stylesheets' means in this context (e.g., CSS, SCSS, Tailwind) and the scope (e.g., selected nodes or entire file).

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?

No guidance on when to use this tool versus alternatives (e.g., 'create_style_guide', 'export_tokens', or sibling tools like 'annotate_colors'). The description does not mention prerequisites, exclusions, or typical use cases.

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