List GPU Trace timeline API events

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

Annotations already declare read-only and idempotent behavior; the description adds useful context about decoded command-stream calls and the meaning of coalesced intervals. This clarifies result semantics beyond the annotations, though it does not detail pagination or result structure.

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 two focused sentences with no filler, front-loading the main action and resource. The second sentence adds a relevant nuance about coalesced intervals without redundancy.

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?

The description covers the core purpose and one nuanced concept, but with 11 parameters, no output schema, and many sibling tools, it omits alternatives, filtering capabilities, and return structure. It is adequate but leaves significant gaps for a tool of this complexity.

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?

With schema description coverage at only 27%, the description needed to compensate for undocumented parameters like limit, offset, sort_by, and the various filters. It only indirectly references timing groups via 'coalesced intervals' but does not map them to exact_timing_only or unique_timing_groups, nor does it explain the other parameters.

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 lists (pages through) queue command-stream calls decoded from .ngfx-gputrace files, including queue identity and timestamp intervals. The specific verb and resource distinguish it from sibling tools like list_gpu_trace_ranges or get_gpu_trace_timeline_event.

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 explicit guidance is provided on when to use this tool versus alternatives like get_gpu_trace_timeline_event or list_gpu_trace_ranges. The description implies it is for browsing timeline events but does not state exclusions or alternative use cases.

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