block

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

Annotations only include readOnlyHint=false and a title, so the description must carry behavioral disclosure. It does reveal that operations include reads and writes (list, insert, update_attribute, define), but it does not explain return values, side effects such as overwriting on define, permissions, or error behavior. This is partial but not complete transparency.

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 description is a compact summary followed by a scannable operation list. Each operation is described in one line with its data structure, and there is no filler or redundant prose. The formatting makes the multiple operations easy to parse.

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?

This is a multi-operation tool with eight parameters and no output schema, so the description needs to cover a lot. It does provide operation inventory and data payloads, but it omits return behavior, coordinate system/units, how entity_id is used, and the full entity schema for define. These gaps make it incomplete for a complex CAD block tool.

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 input schema has zero description coverage and treats data as an opaque object, but the description compensates with operation-specific shapes like insert: {name, x, y, scale?, rotation?, block_id?} and update_attribute: {entity_id, tag, value}. Generic parameters such as doc_id and lease_token remain unexplained, but the most important data parameter is well detailed.

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 'Block definition, insertion, and attribute management,' clearly identifying the resource and core actions. The subsequent operation list (list, insert, get_attributes, update_attribute, define) makes the tool's purpose concrete and distinguishes it from sibling tools like entity or layer. It lacks a single imperative verb but is not vague.

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?

The operation list implies when the tool is appropriate (e.g., 'list all block definitions' or 'insert_with_attributes'), but there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. Usage context is only implied by the operation names.

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