save_bd_design

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: it doesn't say what happens if no design is open, whether it overwrites an existing file or writes to a new path, whether unsaved validation is required, or what the result looks like. Only the basic mutation semantic is conveyed.

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 — the scope ('currently open') is stated immediately. It is perhaps too terse for a persistence operation, but nothing in it is wasted.

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 zero-parameter, no-output-schema tool this is close to sufficient, but with no annotations and no output schema the description should still say what the caller gets back and how failures (no open design, write error) are surfaced.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; baseline is 4. The description correctly implies the save target is implicit (the open design) rather than caller-supplied.

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: saving the currently open block design to disk. It's clear what the tool does, though it doesn't distinguish itself from siblings like close_bd_design (which may also persist state) or create_block_design.

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?

Usage is only implied by 'currently open block design' — the agent can infer it applies only when a BD is open, but there's no explicit guidance on when to save versus when close_bd_design handles persistence, nor any prerequisite or ordering advice.

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