breakpoint_set_data

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

With no annotations, the description solely provides behavioral context. It discloses adapter support limitations and the trigger condition, but lacks details on behavior when unsupported or errors.

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?

Two concise sentences cover purpose, usage, prerequisite, and limitation. No redundancy or extraneous information.

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?

The description is adequate for a simple tool with fully documented schema parameters. It could mention success/failure behavior, but the essential context is present.

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% with good definitions. The description adds value by explaining where to obtain variablesReference and name, and clarifying accessType defaults.

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 sets a data/watch breakpoint and specifies the trigger condition (variable change or read). It distinguishes from sibling breakpoint-setting tools by its specific purpose.

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?

It explicitly requires variablesReference and name from variables_get, guiding the agent on prerequisites. It also warns that not all adapters support it. It does not explicitly exclude alternatives, but the sibling tools cover different breakpoint types.

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