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

Rich operational context is supplied (three starts/account/day, one per site, 170s deadline, 26h report expiry, partial results). However, it directly conflicts with the idempotentHint=false annotation by asserting 'A repeated request reuses today's review' and 'Retries return the same review' — i.e., identical calls produce no new effect. The description also repeats these points multiple times rather than adding coverage.

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 text is highly redundant: the three-starts-per-day rule is stated twice, the single-review-per-day rule twice, and 'Do not claim complete safety from a partial result' is restated as 'Partial results do not establish safety.' Useful facts are buried in repetition rather than front-loaded.

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 mutating, quota-limited, open-world tool with no output schema, the description does cover safety, retries, quota and expiry, which is substantial. But the redundant phrasing and the unresolved idempotency conflict leave an agent unsure how repeated calls actually behave.

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?

There is a single parameter with 100% schema description coverage ('Owned tab ID from list_tabs'), so the schema already carries the semantics. The description adds no meaning for the id argument; baseline 3 applies.

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 states a concrete verb+resource: 'Start a TLS review of the saved HTTPS origin.' This distinguishes it from read-style siblings like connection_review and cancel_connection_review, though it never names them explicitly.

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 conditions (requires account session, X-Organization-Id, CSRF for writes) and one exclusion ('GET never starts a scan'), but the exclusion is phrased about HTTP methods rather than naming the alternative tool, and there is no explicit 'use X instead when...' routing.

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