Add Hierarchical Block

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent write, so the safety profile is covered. The description usefully adds that a child sheet, In/Out pins, and a parent placement are produced, but it omits failure behavior, whether the parent is mutated in place, or what happens on repeat calls.

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 front-loaded sentence with no filler and the action stated first. It is efficient, though its brevity borders on under-specification for a 6-parameter editing tool.

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 hierarchical-schematic mutation with 6 parameters, no output schema, and near-zero schema coverage, one sentence is inadequate. An agent is left guessing what reference, x, and y do and what preconditions must hold before the call.

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 only 17% (only workspace_root is documented), so the description must compensate and does not. Terms like 'child sheet', 'In/Out pins', and 'parent' loosely gesture at block_name/schematic_path, but x, y, and reference are never explained in either the schema or the description.

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 and resource ('Create a child sheet'), plus the side effects of adding In/Out pins and placing it on the parent. It is clear what the tool does, but it never distinguishes itself from nearby siblings like add_component or create_schematic, so an agent can't route on the description alone.

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?

There is no when-to-use guidance, no prerequisites (e.g. whether a parent schematic must already exist or be loaded), and no mention of alternatives like add_component. The agent must infer usage entirely from the name and title.

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