Debugger (CDP)

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

With no annotations, the description carries the full burden and does add one concrete behavioral trait: attaching shows a Chrome debug banner. It does not disclose whether attaching is disruptive, what permissions are needed, whether detach cleans up, or any side effects beyond the banner.

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?

Three short sentences, front-loaded with the core action, followed by capability context and a behavioral note. No wasted words, though the capability list is somewhat enumerative padding.

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 low-complexity toggle with only two parameters and no output schema, the description covers the actions, their purpose, and one behavioral detail. It still omits auth/permission requirements and the relationship to the 'status' sibling, leaving partial gaps for an agent acting without annotations.

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 0%, so the description must compensate. Its verbs 'show, attach or detach' loosely map to the action enum (status/attach/detach), which helps, but the tabId parameter and the default 'status' action are left entirely unexplained.

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?

States a specific verb set (show/attach/detach) and resource (Chrome debugger for a tab), and explains the CDP capabilities it unlocks. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like 'status' which could also expose debugger state.

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?

Usage is implied via the capability list (trusted input, screenshots, evaluation, uploads, emulation) - an agent can infer you attach when those are needed. However, there is no explicit when-to-use guidance, no exclusions, and no mention of the 'status' default action or how it relates to the 'status' sibling tool.

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