Set attribute property values

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds real value by disclosing atomicity ('in one undo step') and the reset/setUndefined semantics, but it never explains what makes the operation destructive (overwriting existing values) or how errors/ambiguity are surfaced.

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?

Front-loads the core action and the undo-step behavior, then gives the entry format and unit rules compactly. No filler, though the inline entry-shape restatement is somewhat redundant with the schema.

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 two-parameter mutation tool with no output schema and annotations covering the safety profile, the description supplies the key operational facts: atomicity, units, classification prerequisite, and reset/undefined modes. Error/ambiguity behavior is left unstated, but nothing critical to calling it correctly is 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?

Schema description coverage is 50%, and the schema itself already elaborates most fields (property formats, units, attribute addressing). The description restates the entry shape and the unit conventions, adding modest meaning but largely duplicating the schema's own value description. Baseline 3 is appropriate.

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: setting property values of attributes, and names the entity type (building materials, ...). It clearly contrasts with the get_ sibling get_attribute_property_values, but does not distinguish itself from set_property_values, which appears to be a closely-related write tool.

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?

Gives one prerequisite constraint — the property must be available for the attribute's classification — which is genuinely useful usage context. However it offers no explicit when-to-use vs the sibling set_property_values, so the agent must infer the split. Usage is implied rather than spelled out.

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