Apply Schematic Layout Spec

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds nothing beyond the mutation implied by "replace" — it does not say what happens to the existing layout/content or whether the operation is reversible, and the word "replace" sits in mild tension with destructiveHint=false without clarifying which reading is correct.

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?

It is a single, front-loaded sentence with no wasted words, which is structurally clean. But for a three-parameter mutation tool the brevity reflects under-specification rather than disciplined conciseness.

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 non-idempotent mutation with no output schema and only one of three parameters documented, the description is too thin: it omits the required parameter, valid spec_name values, and any effect/rollback behavior. Annotations carry the safety profile, but the agent still lacks what it needs to invoke this 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?

Schema coverage is only 33% (only workspace_root is documented). The description names no parameters; "built-in layout" only loosely hints at spec_name, and schematic_path — the sole required parameter — is never explained. With low coverage the description needed to compensate and 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 names a verb (replace) and a resource (schematic) plus the source of the replacement (a built-in layout), so the general intent is inferable. However, "replace a schematic" is imprecise about scope — it reads as overwriting the whole schematic rather than applying a layout spec to it — and it gives no differentiation from the sibling describe_schematic_layout_spec, which an agent must disambiguate against.

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, and no named alternative. With siblings like describe_schematic_layout_spec and suggest_component_placement, the description leaves the agent to guess when this tool is the right choice.

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