set_call_breakpoint

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 mentions the tool sets a breakpoint that triggers on function calls and can be set pre-session, but fails to disclose critical behavioral traits such as whether this requires debug permissions, if breakpoints persist across sessions, what happens on duplicate settings, or any rate limits. This leaves significant gaps for a mutation tool.

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 highly concise and front-loaded, consisting of two clear sentences that directly state the tool's action and a key usage note. There is no wasted verbiage, making it efficient and easy to parse.

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 complexity of a mutation tool (setting breakpoints) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like permissions, persistence, error handling, or return values, which are crucial for effective use in a debugging context.

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 description coverage is 100%, with clear parameter descriptions in the schema (e.g., 'function_name' as the function to break on, 'session_id' as the session ID). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 without compensating value.

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's purpose with a specific verb ('Set a breakpoint') and resource ('when a specific function is called'), distinguishing it from general breakpoint tools like 'set_breakpoint' by focusing on function calls. However, it doesn't explicitly differentiate from 'set_exception_breakpoint' or other sibling tools beyond the function-call scope.

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 some context by mentioning 'Can be set before a debug session starts,' which implies timing guidance. However, it lacks explicit when-to-use vs. alternatives (e.g., compared to 'set_breakpoint' or 'set_exception_breakpoint'), no prerequisites are stated, and it doesn't clarify if this is for active sessions only or other scenarios.

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