List non-zero ACS variables

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

With no annotations, the description must fully disclose behavior. It states it runs a command and returns non-zero variables, but does not mention potential side effects (e.g., is dumpacsvars safe?), required permissions, or what happens if no variables are found. The lack of detail reduces transparency.

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, efficient sentence that conveys the essential information without waste. It is front-loaded with the action and result.

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 tool has no output schema, no annotations, and two parameters with a technical domain (ACS variables), the description is too brief. It lacks information about return format, error handling, and the meaning of the 'instance' parameter. For a complete understanding, the agent would need external knowledge.

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 should add meaning. It only mentions the 'scope' parameter indirectly ('optionally filtered by scope') but does not explain the 'instance' parameter at all. The schema provides enum for scope, but the instance parameter's purpose (e.g., which instance's variables) is left unclear.

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 clearly states that the tool runs `dumpacsvars` and returns all non-zero ACS world/global variables, with optional filtering by scope. This is a specific verb (list/return) and resource (ACS variables), and it implicitly distinguishes from siblings like `get_acs_var` (single variable) and `set_acs_var` (modify).

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. It does not mention that `get_acs_var` or `find_acs_symbol` might be better for specific variable lookups, nor does it state any prerequisites or context for use.

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