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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety bar is lower. The description still adds meaningful context beyond them: it opens nothing by itself, returns a procedural walkthrough rather than data, and notes the absence of a general-purpose vendor API. That is the key behavioral distinction an agent needs.

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 is front-loaded well: purpose, then the browser follow-up. However, the trailing sentence about the vendor not publishing a core API reference, complete with a verification date, is tangential to invoking this tool and reads as filler.

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 zero-parameter, read-only guidance tool with no output schema, the description covers what it returns (screens, buttons, fields) and what it does not do (open anything). An agent has enough to call it and to know the follow-up step; only connection/precondition details are absent.

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, so there is nothing for the description to disambiguate and the baseline is 4. It correctly implies no input is needed from the caller.

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 ('Review shoot One Page details in the user's own Sprout Studio account') and clarifies the output form ('returns how to do it in Sprout Studio step by step (screens, buttons, fields)'). It separates itself from the browser tools by stating it 'opens nothing by itself', though it does not explicitly differentiate from sibling Sprout review tools like the client activity log.

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 two-stage workflow: use this tool to get the step-by-step procedure, 'then do it with the cotlet_browser_* tools'. That is a usable when-to-use signal for choosing this over the browser tools. It stops short of explicit exclusions or prerequisites (e.g. whether the account must already be connected).

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