summarize_tab

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

With no annotations, the description carries the full burden. It explains the tool reads the entire page without truncation, uses a chunk-and-combine summarizer, and returns plain text. It does not mention rate limits or prerequisites like tab loading, but is otherwise transparent.

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 concise, front-loaded with the main purpose, and logically structured with usage context, arguments, and return value. Every sentence adds value 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?

Given the low parameter count and presence of an output schema, the description adequately covers purpose, usage, and return format. It could mention edge cases (e.g., tab not fully loaded) but is largely complete.

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 description coverage is 0%, so the description compensates by explaining `tab_id` as 'the handle from open_tab' and `question` as an optional focus. This adds significant meaning beyond the raw schema, though it could detail valid values.

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 the current page in an open tab, and explicitly distinguishes it from sibling `summarize` (URL-based) and `read_tab` (head-only). It uses specific verb+resource and differentiates from alternatives.

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 advises using this tool after navigation/interaction for a full summary, notes that `read_tab` truncates, and references sibling `summarize`. It provides clear when-to-use context but does not explicitly list all exclusions.

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