layout_copy

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral facts: a saved-ID verification step, an idempotency key, and that the destination browser target is returned for follow-up calls. However 'durable idempotency key' sits uneasily with idempotentHint=false without explaining how retries behave, and 'chart comparison' is opaque.

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 compact sentences, both front-loaded with the operation and the return contract. No filler, though 'chart comparison' reads as unexplained jargon that costs more than it earns.

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?

The return value is stated despite no output schema, which is a plus, and the mutation's verification behavior is sketched. Against a 6-parameter, 4-required mutation with 33% schema coverage and no output schema, the definition still leaves too much implicit about preconditions and failure modes.

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%, so the description must carry weight; it partially does, implying that name must be unique, that the idempotency_key is durable, and that a saved-ID verification occurs (expected_layout_id). It says nothing about target_id, timeout_ms, or save_source, so half the surface is still undocumented in prose.

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 uses a specific verb ('Make a copy') plus a uniqueness constraint, and the tool name layout_copy supplies the resource. But the description itself never says what is being copied (a chart layout?) and the phrase 'chart comparison' is unexplained, so an agent must infer scope from the name rather than from the text.

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 statement of when to use this over layout_create, layout_save, or layout_rename, all of which are close siblings for duplicating/persisting layouts. No prerequisites or exclusion conditions are given, so the agent has to guess at routing.

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