list_variables

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the return shape (variables[], collections[], nextCursor?), clarifies that collections only include referenced ones, and mentions pagination via cursor. This provides sufficient transparency for a read-only list operation.

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 concise with no wasted words. It front-loads the purpose, then leverages bullet-style parameter explanations and examples, making it easy to scan. Every sentence adds value.

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 4 optional parameters, no output schema, and no annotations, the description is complete. It covers the return shape, all parameters with additional context, pagination, and provides diverse examples. No gaps are apparent.

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 100%, but the description adds meaningful details: 'case-insensitive' for filter, 'default 100' for limit, and 'opaque pagination cursor' for cursor. This goes beyond the schema descriptions, adding practical usage information.

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 'List variables as a flat array with referenced collections.' It identifies the specific verb (list) and resource (variables), and the mention of 'referenced collections' differentiates it from other variable-related tools like bind_variable or create_variable, which have different purposes.

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 examples and parameter details, implying usage scenarios, but it does not explicitly state when to use this tool versus alternative listing methods (e.g., if there were a search_variables tool). No guidance on when not to use it or which situations are inappropriate is given.

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