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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description does not need to re-establish safety. It does add non-obvious behavior: the tool 'returns how to do it ... step by step' and 'opens nothing by itself', which tells the agent this is a guidance-producing call requiring a follow-up browser action, not a data fetch. The note that Sprout Studio publishes no general-purpose core API further explains why the browser path is required.

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 and the 'returns steps, opens nothing' caveat are front-loaded and useful. The closing sentence about the official API is awkward and includes an oddly specific vintage ('vendor sources checked on 12 November 2026'), which reads as filler even though the underlying point — no general API exists — mildly justifies the browser workflow.

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 parameters, no output schema and rich annotations, the description carries the remaining burden and mostly does: it says what comes back (step-by-step screens, buttons, fields) and how to proceed afterward. What it does not cover is failure behavior — e.g., what happens if the user is not signed in or the screens differ — but that is a modest gap for a guidance-only, read-only tool.

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 (empty object, additionalProperties false), so there is nothing for the description to disambiguate. Baseline 4 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 uses a specific verb plus resource — 'Review client activity log' — and scopes it to 'the user's own Sprout Studio account', which separates it from the sibling sprout_studio_review_inquiries_and_leads and sprout_studio_review_shoot_one_page_details by resource. It never states the distinction explicitly, but the resource name is unambiguous enough that an agent can pick correctly.

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 a clear workflow: first call this to obtain step-by-step screens/buttons/fields, then act using the cotlet_browser_* tools. That is real when-to-use guidance tied to a concrete next step. It stops short of stating when NOT to use it (e.g., versus the other sprout_studio_review_* tools or cotlet_app_guide).

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