Get Block Attributes

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description adds real value: it documents the return shape as a {TAG: value} dict and discloses the subtle edge case that multi-line attributes are returned with `\P` separators (AutoCAD TextString) on both engines — a genuine behavioral disclosure an agent would not get from the schema.

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 and return type, followed by one narrowly scoped edge-case note. Nothing is redundant and nothing 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?

An output schema exists, so return values needn't be spelled out, and the readOnly annotation covers safety. Combined with the description's return-shape and multi-line notes, an agent has what it needs; only explicit sibling routing (vs. block_set_attributes/entity_get) 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 100% and the single `handle` parameter is documented as a 'Block reference (INSERT) entity handle'. The description's reference to 'a block reference' restates rather than extends that; baseline 3 applies when the schema does the heavy lifting.

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 ('Get all attribute values from a block reference') and even specifies the return shape ({TAG: value} dict). The 'Get' vs. the sibling block_set_attributes is implicitly clear, but the description never explicitly names or distinguishes itself from that sibling, so it stops short of a 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?

No statement of when to use this tool versus alternatives such as entity_get, block_list, or block_set_attributes, and no prerequisites (e.g. the handle must reference an INSERT with attributes). The multi-line note is behavioral, not usage guidance.

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