debuggerVariables

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only indicates a read operation ('Retrieves') but does not state whether it affects the debugger session, what context it operates in, or any side effects. No permissions or response format are mentioned.

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 and front-loaded, but it conveys almost no useful information beyond the name. Under-specification is not the same as conciseness; this sentence adds no value and could be inferred entirely from the tool name and schema.

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 complexity of the debugger tool family and the lack of output schema, annotations, or any explanatory context, this description is severely incomplete. It does not explain the return value, how it relates to other debugger tools, or the role of parent variables in the retrieval.

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?

The input schema has 100% coverage for the sole parameter 'parents,' which is described as 'An array of parent variable names.' The tool description adds no further meaning about how this parameter influences the retrival, but the schema already provides a baseline. Thus a score of 3 is appropriate.

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 states 'Retrieves debugger variables,' which is essentially a restatement of the tool name 'debuggerVariables.' It lacks specificity about which variables (e.g., top-level vs. child) or how it differs from sibling tools like debuggerChildVariables. This is close to a tautology.

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 use this tool versus alternatives. There are no context clues, no mention of prerequisites, and no exclusions. The existence of many debugger-related siblings makes this lack particularly problematic.

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