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

With no annotations, the description carries the full burden and does well: it discloses ordering (newest first), provenance (browser extension), and the returned field set. It stops short of stating how many reviews are returned, any window/limit on 'recent', or explicitly confirming the call is a read-only, side-effect-free operation.

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 compact sentences: the payload description first, then the action guidance. No filler, no redundancy, and the field enumeration doubles as the output documentation.

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?

There is no output schema and no annotations, so the description must stand in for both — and it enumerates the returned fields and the downstream reviewId, which covers the essentials. The remaining gap is result cardinality and any extension-availability prerequisite.

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?

The tool takes zero parameters, which is the baseline-4 case; there are no arguments whose meaning could be ambiguous. The description instead clarifies the output shape, which is a sensible use of space.

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 ('List your recent design reviews') and goes further to name the data source (Design Review browser extension), the sort order (newest first), and the exact returned fields. An agent can distinguish this from get_review and get_latest_review without opening a 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?

'Use this to pick which review to apply' gives a clear intent and explicitly routes the agent to get_review via the reviewId, which is a strong downstream link. It does not, however, contrast with the sibling get_latest_review for the single-most-recent case, leaving that selection to inference.

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