startDebuggingSession

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

With no annotations, the description carries full burden. It discloses return behavior (returns workflow + _ui field to relay verbatim) but doesn't clarify whether this tool performs any side effects — it doesn't say if it establishes a connection/launches a browser, or is purely informational. Given the zero-param nature, the omission is moderate.

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?

Front-loaded with the critical 'CALL THIS FIRST' instruction and clear trigger keywords. The keyword list is long but functional. Slightly verbose but well-structured.

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 zero-parameter informational tool with no output schema, the description tells the agent when to invoke it, what it returns, and how to handle the response (_ui field). This is 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?

Zero parameters, so baseline of 4 applies. Nothing to document; the schema is empty.

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?

Specific verb+resource: 'start debugging session' entry point. Clearly distinguishes from siblings by being the mandatory first call ("CALL THIS FIRST... before any other tool") that returns the workflow. Purpose is unmistakable.

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?

Extremely explicit when-to-use guidance: 'CALL THIS FIRST whenever browser-side debugging is needed — before any other tool.' Also provides an extensive auto-trigger keyword list and explicit exclusion guidance (before other tools).

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