edb_evaluate_expression

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds limited incremental transparency by listing supported operations. It does not detail error behavior, side effects, or limitations, but the annotations cover safety adequately.

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 concise, with the main action in the first sentence, followed by examples and args/returns. It avoids unnecessary detail, though the structured args/returns could be omitted if the schema is the primary reference.

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 presence of an output schema (though not shown), the description adequately covers input and output types. It provides examples and supported operations, but lacks error handling details. For a read-only evaluation tool, this is mostly complete.

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 already provides a description for the 'expression' parameter with examples, so the description's repetition adds little new meaning. The schema coverage is effectively high despite the 0% metric, as the schema includes its own description.

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 'Evaluate a C expression in the debug context' and lists supported operations (variables, pointer dereferences, casts, arithmetic, function calls) with examples. It implies a general-purpose evaluator but does not explicitly contrast with sibling tools like edb_get_variable or edb_call_function, which limits clarity.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it, prerequisites, or context. The description assumes the agent knows when to evaluate an expression versus, for example, reading a variable directly.

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