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, and the description is consistent with them by clarifying the tool only returns guidance and opens nothing. It adds useful context on why a browser flow is required (AestheticsPro publishes no public API). However, it says nothing about failure modes, whether an account connection must exist, or how the steps are scoped to the user's account.

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?

Purpose and the no-side-effects guarantee are front-loaded, followed by the browser handoff. The closing paragraph on AestheticsPro's Enterprise-only API is relevant but long, and the dated parenthetical '(checked 11 Nov 2026)' adds little for an agent deciding how to call the tool.

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 is returned and what must happen next. It stops short of stating prerequisites such as an authenticated AestheticsPro Cloud Browser session or what the response looks like if the account is not connected.

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; the baseline for a parameterless tool applies. No misleading parameter implications are present.

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 and resource and, crucially, clarifies that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the action itself. It does not explicitly distinguish itself from the similarly named sibling aestheticspro_configure_gender_identity_and_pronouns, which leaves some ambiguity.

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 states the follow-on path explicitly: after getting the instructions, execute them via the cotlet_browser_* tools in the AestheticsPro Cloud Browser. It also rules out self-execution ('opens nothing by itself'). No explicit when-not-to-use case or direct naming of the near-duplicate sibling.

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