gdb_load

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It fails to mention whether the operation is destructive, requires a running session, or produces any side effects, leaving the agent without critical safety information.

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 a single sentence, extremely concise. However, it may be too brief, omitting necessary details for a tool with multiple parameters. While front-loaded with the verb and resources, it sacrifices completeness for brevity.

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 tool's complexity (loading multiple artifacts) and lack of annotations, the description is severely incomplete. It does not mention return values (despite an existing output schema), prerequisites, or the effect on the debugging session. The agent lacks essential context to use the tool correctly.

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 0%, so the description must compensate. It merely lists parameter names ('binary', 'core', 'symbol_file', 'args') without explaining their roles or expected formats, adding minimal value beyond the schema's title fields. For example, it doesn't clarify that 'binary' is the path to the executable or that 'args' are command-line arguments.

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 explicitly states the action 'Load' and lists the specific resources: binary, core file, symbol file, and optional program arguments. This clearly distinguishes it from sibling tools like gdb_memory or gdb_register which focus on different aspects of GDB debugging.

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 such as gdb_remote for remote debugging or gdb_exec for execution. It lacks any context about prerequisites or scenarios where loading is appropriate.

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