screenshotAndAnnotate

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

Annotations already indicate readOnlyHint=true, so the description need not repeat safety. The description adds behavioral context by listing what the tool returns (dev server URL, diagnostics, git diff summary, Playwright steps), which informs the agent of the tool's output beyond the name. However, it does not elaborate on any side effects or state changes.

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 sentence that packs multiple elements, making it dense but not easily parseable. It could be improved by front-loading the primary action and structuring the output items more clearly.

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 no output schema, the description lists key outputs (dev server URL, diagnostics, git diff summary, Playwright steps, screenshot) but lacks details on format or structure. It provides a reasonable overview for a complex tool but leaves some ambiguity about the exact return shape.

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% with descriptions for all three parameters. The description does not add additional meaning beyond the schema; it only mentions 'dev server URL' indirectly relating to the url parameter. The agent can infer parameter usage from schema alone.

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 the tool correlates browser and IDE state and captures a screenshot, distinguishing it from the sibling 'captureScreenshot' by emphasizing context gathering. However, the verb 'Correlate' is somewhat vague, and the tool's primary action could be more explicitly stated as capturing an annotated screenshot.

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 is provided on when to use this tool versus alternatives like 'captureScreenshot'. The description does not mention contexts where correlation is beneficial or when to prefer other tools.

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