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

Beyond the annotations (readOnly, idempotent, openWorld=false, destructive=false), the description discloses a great deal: one review per account/org/origin/UTC-day, three starts per day, retries returning the same review, scanner IP sampling, three stages, a 170-second deadline, that partial results do not establish safety, and a 26-hour expiry. This is exactly the behavioral context annotations cannot carry.

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 dense with distinct facts and every sentence carries information, with no filler. It is slightly back-loaded: the auth/CSRF preamble leads rather than the core "read the review" purpose, which would be better 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 one-parameter, read-only tool with no output schema, the description covers timing, idempotency, expiry and results caveats thoroughly. Its only real omission is clarifying the relationship to the sibling review_connection, whose name is nearly identical.

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 only one parameter and schema description coverage is 100%, with 'id' documented in-schema as an owned tab ID from list_tabs. The description adds no additional parameter meaning, which is the expected baseline when the schema already does the work.

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 specific verb and resource: "Read today's private TLS review without starting a scan." That is clear and actionable. However, it does not differentiate itself from the very close sibling review_connection, so an agent cannot tell from the text which of the two to pick.

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?

Usage is implied by "without starting a scan" and the note that "GET never starts a scan", which contrasts with a starting path. But no alternative tool (review_connection, cancel_connection_review) is named, and there are no explicit when/when-not conditions routing the agent between siblings.

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