Get System Variable

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

The readOnlyHint annotation already declares the read-only nature, and the description adds no behavioral detail beyond that, such as behavior for unknown variables, return formatting, or error handling. There is no contradiction, but also no additional transparency value.

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 single, clear sentence with no filler words or redundant information. It is appropriately sized for a simple one-parameter read-only tool.

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?

Given the simple parameter set, readOnlyHint annotation, and presence of an output schema, the description is largely sufficient for an agent to call the tool correctly. It is missing only a brief note about when to prefer this over system_set_variable or system_status.

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 100%, and the single parameter 'name' includes concrete examples like DIMSCALE and LTSCALE. The description itself does not discuss parameters, so it relies entirely on the schema, which is sufficient for a baseline score.

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 states a specific action ('Get') and a clear resource ('AutoCAD system variable value'), making the tool's purpose immediately understandable. It does not explicitly distinguish itself from system_set_variable or other sibling tools, but the get/set contrast is strongly implied by the verb and resource.

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 provides no guidance on when to use this tool versus alternatives such as system_set_variable, system_status, or system_capabilities. It only restates the basic operation without giving context, preconditions, or exclusions.

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