list_breakpoints

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

With no annotations, description carries full burden. It discloses an important behavioral trait: breakpoints listed are only those set via this server (not external ones). Also clarifies scope (main vs renderer). Does not cover other traits like permissions or latency, but sufficient for basic understanding.

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?

Single sentence, no wasted words. Purpose is front-loaded and immediately clear. Perfect conciseness.

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?

No output schema provided, so description should hint at return value (e.g., list of breakpoint IDs or details). It does not. Also, no context about prerequisites (e.g., must have an active session). Adequate for a simple tool, but could be more complete.

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% and already describes both parameters (sessionId required, pageId optional with default 'main'). Description adds no additional meaning beyond schema, which is adequate given high schema coverage.

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?

Description clearly states the tool lists breakpoints set via this server, specifying scope (main process or renderer page). Verb 'list' and resource 'breakpoints' are specific, and it distinguishes from siblings like set_breakpoint or remove_breakpoint.

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 explicit when-to-use or when-not-to-use guidance. Implies usage after setting breakpoints via this server, but does not exclude other scenarios or mention alternatives. Sibling tools like remove_breakpoint or get_paused_state are not compared.

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