query_live_capture_entries

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

No annotations provided, so description carries full burden. It successfully discloses critical cursor behavior ('Does NOT advance the cursor — safe to call repeatedly') and default scanning behavior ('Default cursor=0 scans all captured data'). Missing details on rate limits, auth requirements, or exact return structure, though output schema exists.

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?

Five sentences, zero waste. Front-loaded with purpose, followed by recommendation, behavioral warning, parameter default, and sibling reference. Every sentence earns its place with high information density.

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?

For a 24-parameter complex filtering tool, the description covers the unique behavioral aspects (cursor immobility) and sibling relationships adequately. However, given zero schema descriptions, it lacks explanation of the filtering paradigm, preset meanings, or parameter interactions. Output schema exists, mitigating need for return value description.

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 0% schema description coverage across 24 parameters, the description fails to compensate adequately. It explains cursor behavior specifically but leaves 23 other parameters (host_contains, request_json_query, preset enums, etc.) completely undocumented. No explanation of filtering syntax or preset options provided.

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?

Description opens with specific verb 'Analyze' and resource 'active live capture' plus methodology 'structured summary-first filtering.' It clearly distinguishes from sibling get_traffic_entry_detail by specifying this is for summary analysis versus drilling down.

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?

Explicitly states 'This is the RECOMMENDED tool for inspecting live traffic' and provides clear alternative guidance: 'Use get_traffic_entry_detail to drill down into a specific entry_id.' Also implies when-not by emphasizing cursor safety for repeated calls.

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