get-tab-web-content

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

With no annotations, the description carries the full burden. It usefully discloses the return payload (text + links) and the truncation/offset paging behavior, which is real behavioral context. It stops short of stating read-only nature, permission needs, or how truncation is signalled, so it is adequate but incomplete.

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?

Two tight sentences, front-loaded with what the tool returns before the conditional offset guidance. Every sentence earns its place with no filler.

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 two-parameter, no-annotation, no-output-schema tool, the description covers the return payload, the scoping key, and the paging escape hatch. What is missing is any statement of safety/permission posture, a minor gap given the low 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?

Schema description coverage is 0%, so the description must compensate. It fully explains the non-obvious 'offset' parameter (paging after truncation), which is valuable, but gives no semantics for 'tabId' beyond its self-evident name. Partial compensation over two parameters lands at the baseline.

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?

States a specific verb and resource: returns the full text content plus the link list of a webpage, keyed by tab ID. This clearly distinguishes it from siblings like capture-tab-screenshot (visual) and find-highlight-in-browser-tab (search), so an agent can pick it without opening any schema.

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?

It gives explicit guidance for one parameter ('Use offset only for larger documents when the first call was truncated'), which is genuine when-to-use advice. However, it never says when to reach for this tool versus alternatives such as find-highlight-in-browser-tab or capture-tab-screenshot, leaving the core selection decision implied.

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