get_variables

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

No annotations provided. The description only states the basic function without disclosing behavioral traits like read-only nature, return structure, permissions needed, or side effects. It carries full burden but fails to add value beyond the name.

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?

Single sentence, no redundancy. Could be slightly more informative without losing conciseness, but it's appropriately sized for a simple listing 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?

Despite no parameters, the description is too minimal. It doesn't explain scope (all vs local vs library), return format, or pagination. Given the existence of get_local_variables, ambiguity remains. Lacks sufficient detail for an agent to fully understand the tool's capabilities.

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?

No parameters exist, and schema coverage is 100%. The description cannot add parameter semantics, and per guidelines, zero parameters baseline is 4. No contradiction or missing info.

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 'List all variable collections and their variables' clearly states the action (list) and resource (variable collections and variables). It distinguishes from siblings like create_variable, but there is a sibling 'get_local_variables' which may overlap; explicit scope differentiation would improve clarity.

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?

No guidance on when to use this tool versus alternatives (e.g., get_local_variables). No prerequisites or exclusions mentioned. The agent receives no help in choosing between similar listing tools.

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