sw_set_properties

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

The annotations already declare this is a non-read-only but non-destructive operation, and the description adds useful context by naming the title block and BOM as targets. However, it does not disclose whether existing custom properties are overwritten or merged, whether changes are saved, or how configuration-specific properties behave.

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 wasted words. It is efficient, though its brevity means it omits mutation semantics rather than using space poorly.

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?

Given a mutation tool with annotations, no output schema, and fully documented parameters, the description covers purpose and downstream effect but omits critical setter behavior: overwrite vs merge, save semantics, and configuration handling.

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 the schema already documents doc, properties, and configuration. The description adds no parameter-level detail beyond what is in the schema, which is acceptable at baseline when schema coverage is complete.

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 ('Set custom properties') and adds where the values surface ('drawing title block and the BOM'). It is clearly distinct from the sibling sw_get_properties by name, but the description does not explicitly differentiate the two.

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?

Explains the effect of the properties but gives no guidance on when to use this tool versus sw_get_properties, no prerequisites such as an open document, and no note about when not to use it.

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