Draw set door params

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

Annotations already declare readOnlyHint=false (a mutation), idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds the meaningful qualifier "default," indicating these values apply to subsequently created doors rather than an existing one, but says nothing about scope of effect or whether prior doors are updated.

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 purpose is front-loaded and the tool name phrasing is efficient, but the appended rule citation is unexplained clutter that a reader cannot decode without the bulc_knowledge_search tool. Half the description is opaque rule metadata rather than actionable content.

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?

With annotations covering mutation/idempotency and full schema coverage for both parameters, the description only needs to convey purpose - which it does. It is minimally adequate, though for a config setter it could say where the defaults take effect.

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%; both doorWidth and doorHeight already document units (m) and defaults (0.9, 2.1). The description adds no further parameter meaning, 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 specific verb+resource ("Set default door dimensions") that clearly distinguishes it from siblings like draw_set_wall_params and draw_set_window_params. The word "default" correctly signals a global config setter rather than a per-door edit, but there is no explicit sibling differentiation in the text itself.

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 guidance is given. The cryptic rule citation ("[bulc-mcp rules] EVAC-001, GEO-002 — bulc_knowledge_search") hints at a related tool but does not explain when this setter should be invoked versus alternatives such as add_door or update_obstacle.

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