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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it performs no action and opens nothing itself, and there is no public REST API or webhook to call. However, it does not say what the returned steps look like or whether a Cloud Browser session must already be open, leaving operational gaps for a tool whose whole output is procedural guidance.

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?

Three compact sentences, with the identity of the tool and its do-nothing-itself behavior front-loaded and the API-availability caveat last. The final sentence is clumsily doubled ("Ubersuggest's official API: Ubersuggest has no public REST API"), a small redundancy that costs nothing materially.

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, no-output-schema tool whose annotations already carry the safety and world-scope claims, the description supplies the essential missing piece: this returns a procedure and the execution belongs to the cotlet_browser_* tools. What remains thin is the handoff detail (whether a browser session or a pre-existing audit is required), which would make the definition fully self-sufficient.

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?

Zero parameters and schema coverage of 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is claimed or missing.

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 ("Recrawl site audit in the user's own Ubersuggest account") and explicitly frames the output as step-by-step instructions rather than an executed action. It implies a distinction from ubersuggest_get_site_audit (recrawl vs. retrieve) but never names that sibling, so the differentiation is inferential rather than stated.

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?

Gives clear workflow guidance: this tool yields screens/buttons/fields instructions and "opens nothing by itself," after which the agent should act via cotlet_browser_* tools in the Ubersuggest Cloud Browser. What is missing is the selection rule against the sibling read tool (ubersuggest_get_site_audit) and any prerequisite about needing an existing project/audit to recrawl.

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