set_drawing_properties

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

With no annotations, the description carries the burden and does meaningful work: it discloses that one call mutates two different objects (part and drawing), that 'from part' keys create links so values follow the model, and what the return payload covers. It stops short of saying whether existing title-block values are overwritten or what happens on a name collision.

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?

Compact and front-loaded: the purpose sentence comes first, then the routing rules, then the return behavior. The opening clause is awkwardly worded and the parenthetical interrupts the key list, but no sentence 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?

No output schema exists, and the description compensates by explaining what is returned (each field's current value plus fields with no matching property). Combined with the routing rules this is enough to call the tool correctly; only preconditions such as an open drawing are missing.

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 single parameter is a free-form object with additionalProperties true and 0% schema coverage, so the description must supply all semantics — and it largely does, enumerating which key names route to the part, which to the drawing, and that unrecognized names default to the drawing. It does not describe accepted value types (string vs numeric) for keys like weight or qty.

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: it fills a drawing's title block by writing custom properties. It also explains the internal routing (some properties land on the part, others on the drawing), which distinguishes it from generic annotation tools like add_note or edit_annotation. The phrase 'custom properties its fields show' is slightly opaque, but the follow-up sentences resolve 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?

Usage is implied by the property-name lists, which tell the agent which keys belong here versus on the underlying part. It never explicitly says when to call this instead of add_note, edit_annotation, or set_material, nor does it state the prerequisite that a drawing document must be active.

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