block

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

Annotations indicate readOnlyHint=false, and the description confirms mutating actions (insert, update_attribute, define) alongside the read-only list. It does not disclose side effects, coordinate system, units, or error behavior, but the per-operation breakdown is useful. The tool's mutating nature is implicit and consistent with annotations.

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 well-structured, front-loaded summary with a compact line-by-line operation list. Every line has a purpose, and there is no redundant text. It is easy to scan and references each operation's data shape succinctly.

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?

The tool is a multi-operation convenience wrapper with a minimal schema. The description covers all operations and their data requirements, but misses include_screenshot and has some ambiguity in 'define' (entities: [{type, ...}]). Given the complexity, it is mostly complete for invocation, but a few details would improve it.

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 schema has 0% description coverage, so the description must compensate. It does so by specifying the data payload for each operation (e.g., insert expects name, x, y, scale?, rotation?, block_id?). However, the include_screenshot parameter is not explained, and some value types/units (rotation degrees vs radians) are omitted. Overall, it adds significant meaning beyond the bare schema.

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 clearly states the tool's scope: 'Block definition, insertion, and attribute management' and enumerates six specific operations. Each operation has a distinct verb and purpose, making it easy to identify what the tool does and distinguish it from siblings like layering or entity management.

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 implicitly provides usage guidance: list for definitions, insert for placement, update_attribute for editing attributes, etc. There is no explicit 'when to use vs alternatives', but the context is clear enough for selecting the appropriate operation within this tool. No exclusions or alternative tool references are given.

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