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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false. The description adds genuinely non-obvious behavior beyond that: the tool performs no navigation itself, returns procedural steps (screens, buttons, fields), and hands off execution to the browser tools. The trailing commentary about the gated Partner Platform API is background justification rather than tool behavior.

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 behavior is front-loaded in the first sentences, but the final paragraph about Thumbtack's official Partner Platform API, including a 'checked 11 Oct 2026' date, is tangential and inflates the definition without helping an agent decide or invoke. A tighter version would keep the step-by-step/hand-off facts and drop the API aside.

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 carries the burden of explaining what comes back, and it does so: a step-by-step procedure describing screens, buttons and fields. Combined with annotations that cover the safety profile, an agent has enough to know what it will receive and what to do next.

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 no parameters and the schema is fully closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly conveys that no inputs are required.

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 resource (reviews in the user's Thumbtack account) and, crucially, clarifies the actual mechanism: it 'Returns how to do it in Thumbtack step by step... and opens nothing by itself.' That distinguishes it from an executor, though the tool name 'list_reviews' creates slight tension with a tool that only returns instructions rather than review data.

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 workflow guidance: use this for the procedure, then perform the action with the cotlet_browser_* tools in the user's Thumbtack Cloud Browser. It does not name when NOT to use it or which reviews-related sibling to prefer, but the resource (reviews vs. leads) is clear enough to route correctly.

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