list_variables

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior (default limit 500, total/offset/pageCount) and the exact shape of returned values (valuesByMode, valuesByModeName, defaultValue, modes) — substantial behavioral context for a read tool. It omits any auth/permission notes, preventing a 5.

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 with the core action, then progressively adds filter and flag semantics and paging. It is dense but every clause carries information; the middle parenthetical is long yet justified by being the only explanation of multi-mode return values.

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?

With no output schema and no annotations, the description compensates by detailing the return structure and paging protocol, which is what an agent needs to iterate results. It leaves resolvedType semantics unstated, a minor gap for a 5-param tool.

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 80%, and the description adds real meaning beyond it: it explains what includeValues actually returns across modes and why includeScopes exists. Only resolvedType lacks explanation in both schema and description, keeping it just under a 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 with scope: 'List local variables in the current file'. The 'local' and 'current file' scoping, plus the resolvedType filter, distinguish it from siblings like list_variable_collections and get_variable.

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 concrete guidance on when to set includeScopes and includeValues ('use this to read theme/dark-mode values, not just the default mode') and how to page. It does not explicitly name a sibling alternative or an exclusion case, so it falls short of a 5.

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