autocad_set_block_attribute

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the return payload shape ({"status": "updated", ...}), which is useful, but it never explains what the destructive flag implies (overwrite of existing text) or what happens when the tag does not exist on the block.

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-loaded single-sentence purpose followed by a compact Args/Returns block; nothing is padded. Minor redundancy with the schema property descriptions is the only waste.

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 the Returns restatement is optional rather than required. For a destructive mutation, however, the description omits the key operational context an agent needs: that the referenced INSERT must already own an attribute with that tag, and whether undo is available to reverse the change.

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 Args block restates handle, tag and value with essentially the same wording the schema already carries for each property (including the hex-handle pattern note). It adds no syntax, format, or edge-case detail beyond the schema, so it neither compensates for the reported coverage gap nor improves on structured data.

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 one attribute value on a block reference (INSERT entity). The 'one attribute' phrasing subtly differentiates it from the sibling autocad_list_block_attributes, though it never names that sibling directly.

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 only implied: the agent must infer that a block reference handle (from a create/query tool) and an existing attribute tag are prerequisites. No when-not conditions or alternatives (e.g. list_block_attributes to discover tags, insert_block to create the reference) are named.

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