get_variable

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

No annotations are provided, so description carries the full burden. It states it 'gets' a value, implying a read operation, but does not mention any side effects, state changes, or error conditions (e.g., variable not found).

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 very short (one line plus example), but it repeats 'sid — required session ID' which is already in the schema. Could be more efficient by omitting redundancy, but not overly verbose.

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 getter tool with 2 parameters and full schema coverage, the description is adequate but minimal. It does not explain what happens if the variable doesn't exist or the session is invalid, which would be helpful for agents.

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%, so the schema already documents both parameters. The description adds an example of usage but does not add semantic meaning beyond what the schema provides (e.g., format of 'name' or constraints). Baseline 3.

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 'Get value of a stored variable', which is a specific verb-resource pair. It distinguishes from siblings like list_variables (list all) and symbolic tools by focusing on retrieval of a single 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?

No explicit when or when-not to use. The example and mention of 'required session ID' imply context, but no guidance on alternative tools like list_variables for enumerating variables.

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