autocad_delete_entity

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the genuinely useful fact that the deletion "cannot be undone via MCP" — valuable given autocad_undo exists as a sibling. It also states the exact success payload shape. It stops short of describing failure behavior for stale/invalid handles.

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 action sentence followed by the irreversibility warning, then compact Args/Returns blocks. The Returns block is largely redundant given an output schema exists, costing it a point, but nothing padding-like is included.

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 destructive, single-target mutation the irreversibility note is the key disclosure and it is present, and return values need not be explained since an output schema exists. What is missing is routing to the bulk sibling and any note on behavior with an invalid or already-deleted handle.

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?

With one parameter and reported 0% schema description coverage, the description does explain the handle is hex and originates from a create/query tool. That said, the embedded schema field description says essentially the same thing, so the added value over structured data is minimal — enough to reach, not exceed, the baseline.

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?

"Delete one entity by handle" gives a specific verb and resource, and the word "one" implicitly separates it from the bulk autocad_delete_entities sibling. However, it never names that sibling, so the distinction must be inferred rather than read.

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 description offers no when-to-use guidance and never mentions autocad_delete_entities, the obvious alternative for multi-entity deletion. An agent must guess whether to loop this tool or switch to the plural one, and no preconditions (e.g. drawing open, valid handle) are stated.

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