extract_component_set

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

No annotations are provided, so the description carries the full burden. It usefully discloses that propertyName is 'best-effort' (i.e., may silently fail) and that nodes are destructively converted into components, but it omits permissions, reversibility, and what happens to the original frames/nodes.

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 dense sentence, front-loaded with the core action and followed by the mechanism and the propertyName hint. No filler, though the run-on clause structure slightly reduces scannability.

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 complex, mutating, 8-parameter tool with no annotations and no output schema, the description explains the transformation but leaves most parameters, permissions, and failure modes unaddressed. It is not sufficient on its own to call the tool 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?

With 8 parameters at 0% schema description coverage, the description should compensate, yet it only addresses propertyName. The seven others (gap, gapX, gapY, name, columns, parentNodeId, nodeIds) are undocumented in both schema and description, so an agent cannot infer layout or naming behavior.

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?

States a specific verb+resource ('Convert multiple existing frames ... into a variant component set') and explains the mechanism: frames become COMPONENTs then combined into a COMPONENT_SET via combine_as_variants. An agent can distinguish this from the sibling combine_as_variants, which only combines pre-existing components.

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 only usage guidance is for propertyName ('set ... to attempt adding a VARIANT property'), with no explicit statement of when to pick this tool over combine_as_variants or create_component_from_node. Usage is implied by the described pipeline rather than spelled out.

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