Discover source maps

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

With no annotations, the description must carry the burden of behavioral disclosure. It mentions the data source (Debugger.scriptParsed events and script tails) which gives some insight, but fails to disclose whether the tool attaches listeners, waits, is one-shot, or returns results. The waitMs parameter hints at a wait behavior, but the description doesn't explain this.

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?

The description is a single, well-structured sentence that leads with the action and object. It is concise, informative, and free of redundant details.

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?

Given there is no output schema and no annotations, the description should explain return values and prerequisites. It doesn't mention what is returned (e.g., a list of discovered URLs) or any session requirements. The description is too sparse for a tool with 3 parameters and no further specs.

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%, and the description does not explain any of the three parameters (sessionId, waitMs, targetSessionId). The mention of Debugger.scriptParsed events implies sessionId relates to a debugger session, but no explicit meaning is added. The description does not compensate for the lack of schema descriptions.

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 a specific action ('Discover') and resource ('sourceMappingURL values') with a precise source ('Debugger.scriptParsed events and collected script tails'). This distinguishes it from sibling tools like sourcemap_fetch_and_parse or sourcemap_coverage, which target different aspects of source map handling.

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?

The description provides a clear context for when to use this tool: when you need to discover sourceMappingURL values from browser debugger events and script tails. It doesn't explicitly mention alternatives or exclusions, but the context is sufficiently clear to avoid confusion with sibling tools.

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