chrome_scroll_jank_summary

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

Discloses read-only nature, behavior on empty results, and operates on loaded trace. No annotations provided, so description fully handles transparency with clear limits and data source.

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?

Concise yet comprehensive: four sentences cover purpose, output columns, sorting, usage guidance, limitations, and empty results. No wasted words.

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?

Fully explains output schema (column list, order, limit), empty result interpretation, and data source. Despite no output schema field, description provides complete context for correct invocation.

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?

No parameters exist; description explicitly states 'none' and explains operation context. Schema coverage is 100%, so no additional param info needed.

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 summarizes worst scroll jank frames from Chrome traces, listing specific columns and sort order. It distinguishes itself from sibling tools like execute_sql by specifying its focused scope.

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?

Explicit usage guidance: when investigating jank reports or scroll regressions, and when not to use (non-Chrome traces, need more than 100 rows). Suggests alternative tool execute_sql for extended needs.

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