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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false; the description reinforces mutability only indirectly via 'editable session state'. It never states that existing session content can be overwritten, never mentions that external URLs are fetched, and never mentions the private session token — details that live only in the schema, not the description.

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, no waste, and the core action is front-loaded before the co-existence note. Nothing is padded.

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 destructive, open-world tool with a large nested options object full of aliases and no output schema, the description is thin: it does not explain what is returned, what happens to already-loaded designs, or how the options aliases differ. It covers the happy path but not enough for confident invocation.

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 description coverage is 100%, so baseline is 3. The description adds the useful format signal that either a design key or a saved-design URL is accepted, but it gives no guidance on the alias cluster (key/keys/designKey/designkey/designKeys) or on areaId/elementId selection.

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 (load) and resource (SSD design key / streetshirts saved-design URL) and the effect (into editable session state). An agent can tell this opens an existing saved design rather than creating one, though it never explicitly contrasts with change_design or get_design_session which sit right next to it.

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?

'Different saved designs can coexist in one session' is a usage hint implying this may be called repeatedly, but there is no explicit when-to-use, when-not-to-use, or named alternative (change_design, preview_design, get_design_session). Usage must be inferred.

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