create_component

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

Annotations indicate mutation but non-destructive. Description adds: preserves node position/parent, handles fromNodeId, returns { ok, nodeId, name, type }. No contradictions, but lacks detail on potential side effects.

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 sentences, front-loaded with purpose. Second sentence is long but packs essential details (two modes, placement, return value). Minor improvement possible in breaking up.

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?

Covers core behavior, both modes, optional parameters, and return schema. Missing details like default sizing or invalid fromNodeId, but sufficient for typical use.

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 low (29%). Description explains fromNodeId and parentId well, and implies x,y,width,height are for sizing/positioning. Does not detail all parameters but adds meaningful context.

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's purpose: 'Create a reusable main component.' It distinguishes between creating from an existing node or empty, and mentions the follow-up action 'create_instance', differentiating it from siblings.

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?

Explicitly guides when to use 'fromNodeId' vs omit, and recommends 'create_instance' for reuse. Provides context on default parent (current page) and keeps position unless overridden.

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