gdb_call_function

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

With no annotations provided, the description carries the full burden of disclosing side effects. The WARNING explicitly states this executes code in the debugged program, which is critical behavioral information. It could further clarify return value handling or thread context, but covers the essential safety concern.

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 sentences: one stating purpose, one providing a critical safety warning. Zero redundancy, front-loaded with the verb, and every word 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?

Given the high schema coverage and lack of output schema, the description is adequate. However, for a tool performing arbitrary code execution, it could mention prerequisites (process must be stopped) or return value behavior without violating conciseness.

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 coverage is 100% with clear examples ('printf("hello\n")'), so the structured schema fully documents the parameter. The description does not add semantic information beyond what the schema provides, which is appropriate given the high schema coverage.

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 specific action ('Call a function') and the target ('in the target process'), distinguishing it from siblings like gdb_evaluate_expression (inspection) and gdb_execute_command (GDB CLI commands).

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 WARNING about executing code provides strong implicit guidance about when to use this (intentional execution) versus inspection alternatives. However, it does not explicitly name gdb_evaluate_expression as the non-executing alternative.

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