Draw set window params

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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false, so the safety profile is covered. The word "default" in the description adds the useful behavioral fact that this mutates a persistent default rather than a specific window, but nothing is said about scope of effect or interaction with existing windows.

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?

The core sentence is appropriately terse and front-loaded. However the appended rule-code tag (EVAC-001, GEO-002 with a quoted id) is cryptic noise that consumes space without communicating anything an agent can act on.

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-required-parameter setter with full schema coverage and annotations covering safety and idempotency, the description is minimally viable. It is still missing scope-of-effect and any mention of how these defaults interact with add_window, which is the main behavioral question for this tool.

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% and each parameter already documents its unit (m) and default value (1.2/1.2/0.9). The description adds no units, ranges, or semantics beyond the schema, so the baseline 3 applies.

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 clear verb+resource ("Set default window dimensions") that distinguishes it from the sibling draw_set_wall_params / draw_set_door_params family. However it does not clarify whether these defaults apply only to newly drawn windows or retroactively to existing ones, which is the one ambiguity an agent would care about.

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?

No when-to-use, prerequisites, or alternative-selection guidance. The trailing "[bulc-mcp rules] EVAC-001, GEO-002 — bulc_knowledge_search" fragment is an opaque cross-reference rather than actionable usage instruction; an agent cannot infer when this tool should be preferred over simply passing dimensions to add_window.

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