gdb_run_control

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

No annotations provided, so the description must fully disclose behaviors. It lists actions but does not describe side effects (e.g., 'kill' terminates the program, 'interrupt' pauses). No mention of safety, state changes, or required privileges.

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 line listing actions, which is concise but lacks structure. It could be organized into categories or bullet points for clarity.

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 (multiple actions, 6 parameters, no annotations), the description is insufficient. It does not explain return values (though output schema exists), prerequisites, or typical use cases. An agent would need significant additional inference.

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 has 6 parameters with 0% description coverage, and the description adds no parameter explanations. For example, 'action' is required but not elaborated; 'count', 'args', 'stdin', 'timeout', 'confirm' have defaults but no meaning. The description fails to compensate for the missing schema documentation.

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 lists multiple actions (Run, continue, step, next, etc.) that clearly indicate it controls GDB execution flow. It distinguishes from sibling tools like breakpoints or memory inspection. However, it does not explicitly state the resource (e.g., 'debugged program'), making it slightly less specific.

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 on when to use this tool versus alternatives or which action to choose for a given scenario. The description lacks usage context, prerequisites, or exclusions.

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