web

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: field values including passwords are never read, codes/tokens/emails/numbers are masked, banking/payment/identity apps are never read, and background Chrome is frozen. This materially changes how an agent interprets results.

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 core purpose is front-loaded, but the body is a dense run-on paragraph mixing semantics, privacy, and platform caveats without structure. Information is mostly load-bearing, yet the wall-of-text format makes it harder to scan than it needs to be.

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?

With no output schema, the description does explain what read returns (page text, title, address, links) and the privacy masking applied. It is short of describing the exact shape/ordering of the returned data, but it is sufficient to call the tool correctly.

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 carries the full burden and does: tab maps to 'tab=N from tabs', query is line filtering, action selects read vs tabs with read as the default. That fully compensates for the undocumented schema.

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 concrete verb and resource ('read web pages... text of the page, title, address and links') and enumerates the two actions (read, tabs), so an agent can distinguish it from siblings like capture or look. It stops short of naming those siblings or drawing an explicit boundary.

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?

Gives clear usage context: default target is the foreground app's page, alternate is 'tab=N from tabs', and 'query: keep only the lines containing this text'. It also flags the operational constraint that Chrome only answers in the foreground. No explicit when-not-to-use relative to siblings.

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