autocad_insert_block

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

Annotations already declare readOnly=false, idempotent=false, and destructive=false, so the safety profile is covered. The description adds that a new INSERT entity is created and returns a JSON status/handle, but it does not disclose side effects such as layer auto-creation or external file import behavior. With annotations carrying the safety burden, this is adequate but not rich.

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 purpose sentence is front-loaded and the Args/Returns structure is clear and scannable. The Args list is necessary given the nested parameter object. The Returns block is somewhat redundant because an output schema exists, but it is not wasteful enough to lower the score further.

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 block-insertion tool with a nested parameter object and mutation annotations, the description supplies the core action, all parameter semantics, and the return shape. It does not cover error cases or usage routing, but an output schema and the annotations already carry much of the remaining burden.

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 description documents all nested fields with types, defaults, and constraints, including that rotation is in degrees counter-clockwise positive and that x/y/z scale values must be positive. It also adds backend nuance about COM accepting .dwg, which is not obvious from the top-level schema signal. It largely mirrors the schema's own $defs descriptions, so it is strong but not fully additive.

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: 'Insert a block reference.' It also distinguishes the two insertion modes (defined block name vs. external drawing file path). However, it does not contrast itself with any sibling tool, so it falls short of the top score.

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?

There is no explicit when-to-use guidance, no when-not-to-use guidance, and no alternatives named. The description implies usage from the operation itself but leaves routing decisions entirely to the agent.

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