list_variables

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

With no annotations provided, the description carries the full burden of disclosure. It states that the tool lists all global variables and returns their current values, clearly indicating a non-mutating read operation. It does not detail authentication or rate limits, but for a zero-parameter read-only list tool, the description sufficiently conveys the behavioral scope.

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 two sentences plus an example, front-loaded with the core purpose. Every sentence contributes: the first defines the action and output, the second provides usage context and example phrasing. There is no padding or redundancy.

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 simple tool with no parameters and no output schema, the description is complete enough: it states what is listed, includes the current values, and gives usage context. It does not detail the exact return format or edge cases like empty results, but these are not critical for a zero-parameter list 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?

The tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description adds no parameter details, but none are needed since the schema already fully describes the input as an empty object.

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 uses a specific verb ('List') and resource ('all global variables with their current values'), and clearly distinguishes this from sibling tools like list_websites or list_contacts. The scope is explicit: global variables used in templates, workflows, and agent prompts.

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 clear context by explaining that these variables are used in templates, workflows, and agent prompts, and gives example user queries ('Show my global variables' or 'What variables are set?'). It does not explicitly mention when not to use this tool or name alternatives, but no direct alternative exists among siblings.

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