autocad_list_modelspace_entities

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

With no annotations, the description carries the full burden and does disclose meaningful context: entities come from the live AutoCAD document and results honor the current binding. It is silent on read-only safety, whether the limit is a cap vs. required, and pagination/ordering behavior, so a fair but incomplete picture.

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?

Three short sentences, front-loaded with the core action and scope. The disambiguating sentence earns its place; there is no filler, though slightly more could be said about the filters without bloat.

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 no-annotation, no-output-schema list tool, the description covers scope and the sibling distinction but leaves the return payload (entity types, handles, attributes) and filter semantics entirely unspecified. Adequate as a minimum-viable definition, not complete.

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 0%, so the description must compensate, but it merely repeats the property names (layer, objectName, limit) with no added meaning — no matching semantics for layer, no admissible objectName values, no explanation that limit caps result count. An agent learns nothing beyond the raw schema keys.

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+resource (list entities) scoped to the live AutoCAD document's ModelSpace, and explicitly distinguishes itself from the similarly named internal list_entities sibling. An agent can tell which entity-listing tool to reach for without opening a schema.

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?

Gives a clear operating condition ('respecting the current binding') and names the alternative it is not (the internal CAD session's list_entities). It does not, however, address other plausibly overlapping siblings such as autocad_list_documents or find_entities_by_layer, so routing is only partially disambiguated.

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