variables_get

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

No annotations provided, but description fully discloses behavior: recursive expansion up to depth levels and truncation at maxChildren. Also mentions defaults for all parameters and frameId context.

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?

Two concise sentences with no fluff. Every word is informative: defaults, behavior, parameters all covered efficiently.

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?

Covers input behavior well given no output schema. Could mention return format implications (e.g., structured variables) but not a critical gap for agent usage.

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?

Input schema covers 100% of parameters with individual descriptions. Description adds value by summarizing expansion and truncation behavior, giving context beyond schema.

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?

Description clearly states 'Get variables for a stack frame' with specific verb and resource. Distinguishes from siblings like variables_set (set) and evaluate (expression evaluation) by focusing on reading stack variables.

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?

Describes default behavior (topmost frame, last-stopped thread) and parameters. However, does not explicitly state when not to use or compare with alternatives like evaluate or stack_explore.

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