View all breakpoints and watchpoints with their hit counts to track code execution during debugging.
List breakpoints/watchpoints with hit counts.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "pet_break_list"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| session | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry behavioral info. States output includes hit counts, but lacks details on side effects, session boundaries, or behavior with no session specified.
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?
Extremely concise with no superfluous words. However, the brevity omits essential information about the session parameter, making it slightly less effective despite efficient phrasing.
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?
For a simple list tool with one undocumented parameter and no output schema, the description fails to provide enough context for correct invocation. The session parameter is critical but unmentioned.
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 0% and description does not explain the sole parameter 'session'. The agent has no information on its purpose, allowed values, or default behavior.
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 uses specific verb 'List' and identifies exact resources 'breakpoints/watchpoints' with a notable detail ('with hit counts'). Clearly distinguishes from sibling tools like pet_break_add (add) or pet_break_remove (remove).
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 guidance on when to use this tool vs alternatives. Does not mention prerequisites, session scope, or comparison with watchpoint listing tools like pet_watch_add.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.