evaluate_expression

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

No annotations are provided, so the description carries full burden. It discloses that expressions can modify state, but does not mention failure modes, return values, or side effects beyond modification (e.g., if expression crashes).

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 filler. Every word adds value: 'Evaluate expression in the current debug context' sets purpose, and 'Expressions can read and modify program state' adds behavioral context 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?

Given the complexity of expression evaluation and the absence of an output schema, the description lacks details on how results are returned, error handling, or limitations. With 20 sibling tools, more context would help differentiate 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?

Schema description coverage is only 33% (only frameId has a description). The tool description does not compensate by explaining sessionId or expression parameters, leaving their meaning and constraints unaddressed.

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 the verb 'Evaluate' and the resource 'expression in the current debug context'. It also notes that expressions can read and modify program state, which distinguishes it from read-only sibling tools like get_variables or get_local_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?

The description implies usage for both inspection and modification of program state, but does not explicitly compare to sibling tools or provide guidance on when to use evaluate_expression over alternatives like get_variables or set_variable analogs.

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