edb_disable_lazy_binding

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

The description adds behavioral context beyond annotations: it explains that when lazy binding is disabled, all shared library symbols are resolved at startup, which improves breakpoint reliability. This complements the annotations (destructiveHint, idempotentHint) without contradiction.

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 concise and well-structured, with a clear purpose statement, an analogy to the UI, and a brief explanation of the effect. The Args and Returns sections are tidy, though the Returns section could be more informative than just 'str: Confirmation'.

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 simplicity (one boolean parameter), the description covers the key behavioral impact and parameter meaning. The presence of an output schema (implied) reduces the need to detail return values. It is sufficiently complete for an agent to understand and 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?

The schema already provides a description for the 'disable' parameter ('True = disable lazy binding, False = enable lazy binding'), so schema coverage is effectively 100%. The description's Args section restates this without adding new semantics, thus meeting the baseline but not exceeding it.

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 tool disables or enables lazy binding for the debugee, explaining its effect on symbol resolution and breakpoint reliability. It is specific and distinct from siblings, though it does not explicitly differentiate itself from related tools like edb_configure_debugger.

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 explains when to use the tool (to make breakpoints on library functions more reliable) and references the corresponding UI checkbox. However, it does not provide explicit 'when not to use' guidance or mention alternatives, leaving usage context somewhat implicit.

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