Get Variable

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

With no annotations, the description carries full behavioral disclosure burden, but it only states 'Get one variable' without explicitly confirming read-only semantics, permission needs, or error behavior. The 'get' verb conventionally implies non-destructive access, providing a minimal baseline, but no additional behavioral context is offered.

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 entire description is a single sentence containing no filler or repetition. It front-loads the action and communicates the core purpose instantly.

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 read-by-ID tool with a fully documented input schema and an output schema, the description is minimally adequate. However, it omits any reference to when to use it over list_variables or how the request should be constructed beyond the schema, leaving a noticeable context gap.

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?

All four parameters are fully documented in the schema (100% coverage), each described as a numeric ID, so the description adds no parameter-level meaning beyond the schema. The hierarchical relationship among account, container, workspace, and variable is not explained, but this is not required given complete schema coverage.

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 the specific verb 'get' with the resource 'variable' and the qualifier 'one', clearly distinguishing this singular retrieval from the sibling list_variables. While it does not name alternatives, the singular scope is immediately obvious.

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 choose this tool over siblings such as list_variables, create_variable, or get_workspace. There is no mention of typical use cases, prerequisites, or exclusions. The agent must infer context from the tool name alone.

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