nx_set_attribute

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

With no annotations, the description carries the full burden. It does add real behavioral detail beyond the schema: typical attribute names and the note that values may contain spaces. However, it never states whether setting an existing name overwrites the previous value, whether new attributes can be created this way, or what happens if no part is open — material gaps for a mutation tool.

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 action is front-loaded in the first sentence, followed by a compact rationale and examples. Four short sentences with no filler, though the example list of Chinese names is slightly long relative to the rest.

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?

An output schema exists, so return values need not be explained, and both parameters are named in the text. But for a two-required-parameter mutation with no annotations, the description omits overwrite semantics and preconditions, which an agent would need in order to call it safely.

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 0%, so the description must compensate, and it partly does: it gives typical values for 'name' (名称 / 图号 / 材料 …) and clarifies that 'value' may contain spaces. It still doesn't say whether 'name' is free-form or must match an existing attribute, leaving the key semantic question unanswered.

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?

The description opens with a specific verb+resource ('Set a string attribute on the part') and then explains the downstream purpose (populating title-block cells via part attributes). That is well beyond a tautology. It does not explicitly contrast with the read counterpart nx_list_attributes, so it stops short of 5.

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?

'This is how a title block gets its CONTENT' implies the use case (populating title-block fields) without stating when to prefer this over alternatives or what preconditions apply. There is no when-not guidance and no mention of prerequisites such as an open part or an existing title block.

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