SetPropertyValuesOfElements

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this mutates data; the description's added value is the note that it also applies to subelements of hierarchal elements, which expands the blast radius understanding. However, it says nothing about whether existing values are overwritten, whether the operation is undoable, or what happens on partial failure — meaningful gaps for a destructive bulk write.

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?

Two short sentences, front-loaded with the core action, with the hierarchical-element caveat second. The '(Tapir, Property Commands)' provenance tag adds little but costs almost nothing.

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 single-parameter, destructive batch mutation with no output schema, the description omits failure behavior, overwrite semantics, undo support, and permission/auth needs. The one parameter is also undocumented in prose. This is under-specified for the operation's risk profile.

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 reported at 0% for the single top-level parameter, and the description contributes nothing about the elementPropertyValues structure, the element/property/value triple, or that multiple values can be set in one call. The nested $defs do carry their own descriptions, so the schema is not opaque, but the description itself does no compensating work.

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 gives a specific verb+resource ('Sets the property values of elements'), which cleanly pairs against the sibling GetPropertyValuesOfElements, and it adds a scope note about subelements of hierarchical elements. It does not explicitly name a sibling alternative, but the purpose is unambiguous from the name plus first sentence.

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?

There is no when-to-use guidance, no prerequisites, and no routing against the many adjacent mutation tools such as SetClassificationsOfElements, SetGDLParametersOfElements, or ChangeSelectionOfElements. The only contextual hint is the parenthetical '(Tapir, Property Commands)', which signals provenance but not selection criteria.

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