create_spec_sheet

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a creation action ('Generate') but does not state whether it creates a new node, modifies the frame, overwrites existing sheets, or has side effects on the canvas.

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?

A single sentence that is front-loaded with the action and resource, then specifies content and placement. Every word earns its place, and there is no redundant or filler phrasing.

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 two-parameter tool with full schema coverage, the description is minimally adequate: it names the target, output content, and placement context. However, with no annotations and no output schema, it leaves side effects and invocation prerequisites unstated, so it is not fully complete.

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%, with nodeId described as 'Frame to spec' and position described as 'Where to place spec (default: RIGHT)'. The tool description adds context about the output contents but does not need to explain parameters further because the schema already covers them.

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 states a specific verb ('Generate') and a specific resource ('design specification sheet next to a frame'), and lists the contents ('measurements, colors, and typography'). It is clear about what the tool produces, though it does not explicitly contrast itself with siblings like export_design_specs or create_style_guide.

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 is given about when to use this tool versus alternatives such as export_design_specs, annotate_dimensions, or create_style_guide. The description implies 'use this when you want a spec sheet on the canvas,' but provides no exclusions or selection criteria.

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