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

With no annotations, the description carries full burden. It implicitly conveys a read-only listing and discloses return contents (name, aliases, description), which is useful, but says nothing about whether an active drawing is required, pagination, or result size.

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?

Two sentences, front-loaded with the core action and output, followed by the optional-filter semantics. No filler sentences and nothing repetitive.

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 one-parameter read tool with no output schema and no annotations, the description covers what is returned and how the filter behaves, which is most of what an agent needs. The missing piece is workflow context — e.g. using this to discover commands before calling cad_run_commands.

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 coverage is 0%, so the description must carry the lone parameter — and it does well: it explains that the filter matches the name, an alias, OR words in the description, backed by concrete examples. It omits edge details such as case sensitivity or partial-match behavior, so not a full 5.

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 ('Lists every implemented AutoCAD command') plus what the listing contains (aliases and description). The verb 'list' implicitly separates it from write/execute siblings like cad_run_commands and cad_execute_script, but no sibling is named explicitly.

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?

Usage is only implied: the filter examples ('layer', 'dim') suggest a discovery/lookup purpose, but the description never states when to call this versus cad_run_commands or cad_execute_script, and no prerequisite (e.g. a drawing must be open) is mentioned.

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