LLDB_LOAD

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral details such as whether loading resets the debugger state, requires a stopped target, or any side effects. Simply stating 'load' is insufficient.

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 extremely concise with a single sentence. While it is not verbose, it is arguably too sparse and could benefit from a bit more context without becoming wordy.

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 no output schema and 3 parameters, the description is incomplete. It does not explain the result of loading (e.g., session becomes ready), whether arguments are validated, or any preconditions. More detail is needed for a loading operation.

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%, so the description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate as the schema already describes sessionId, program, and 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 'Load a program into LLDB' clearly specifies the action (load) and resource (program into LLDB). It effectively distinguishes from siblings like LLDB_ATTACH (attach to process) and LLDB_LOAD_CORE (load core dump).

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 usage guidelines are provided. The description does not indicate when to use load versus alternatives like attach or start, nor does it mention prerequisites (e.g., need for an existing session).

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