browser_query_timeline

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool queries a timeline and operates on a session, but does not state that it is read-only, discuss auth requirements, performance impact, or what happens to the session. The description is sufficient for basic understanding but lacks detail on behavioral traits.

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 extremely concise, with a clear header 'TRACE-AS-DATABASE', a one-sentence purpose, illustrative examples, and a closing remark about session state. Every sentence is purposeful and there is no redundant or filler content.

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 the tool has 9 parameters and no output schema, the description provides a good high-level overview and examples but does not explain the return format, pagination, or error cases. It is adequate for a query tool but lacks some completeness for an agent to fully understand the output behavior.

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?

The input schema has 100% coverage with descriptions for each parameter, so the baseline is 3. The description adds value by providing usage examples (e.g., '{ kind: "network", statusGte: 500 }') and explaining how parameters like 'textContains' work, which enhances understanding beyond the 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 the tool's purpose: querying the recorded session timeline for events matching a predicate, with specific examples like network errors and console errors. It distinguishes from siblings by focusing on querying rather than exporting or managing sessions, but does not explicitly differentiate from 'browser_get_timeline' which likely retrieves the full timeline.

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 context on when the tool operates (loaded past session or live session) but gives no guidance on when to use this tool over alternatives such as 'browser_get_timeline' or 'browser_dump_dvr'. There is no discussion of prerequisites, limitations, or when not to use it.

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