evaluate

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'live inferior' and 'PIE-aware' but does not disclose whether evaluation can have side effects, whether the inferior must be stopped, what happens on errors, or what the result format is. For a tool that could potentially execute function calls in gdb, this is a significant transparency gap.

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 one focused sentence that front-loads the core action and resource, then provides illustrative examples. No wasted words; every part earns its place.

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?

With no output schema, no annotations, and only sparse parameter documentation, the description does not fully equip an agent to call the tool correctly. Missing details include return value structure, error behavior, session_id semantics, and whether a stopped inferior is required or evaluation may mutate state.

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 0%, so the description must compensate. It does add meaningful semantics for the 'expression' parameter through concrete examples, but it gives no guidance for the optional 'session_id' parameter. The expression examples are valuable, but the parameter guidance remains partial.

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 a specific verb ('Evaluate') and resource ('a gdb expression against the live inferior'), and adds the distinctive 'PIE-aware' qualifier. The concrete examples (main, &puts@got, $rax+8, *(char**)0x404000) make the tool's purpose immediately recognizable and distinguish it from sibling tools like read_memory or read_registers.

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 context: it evaluates arbitrary gdb expressions on the live inferior, which suggests it is the general-purpose option compared to more targeted sibling tools. However, it does not explicitly state when not to use it or name alternatives, so the guidance is clear but not fully explicit.

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