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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself' and that a separate browser toolset performs the action. It also explains the return shape (screens, buttons, fields) and why the browser route is required: AestheticsPro sells only custom Enterprise API work with no public docs or self-serve keys. That is genuine context beyond the annotations.

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 two clauses, which is good. But the trailing sentence on Enterprise pricing and the 'checked 11 Nov 2026' datestamp is verbose justification padding that does little to help an agent decide or invoke, and the 'ChatGPT, Claude or any AI agent' phrasing is 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, that it performs no action, and what the caller must do next. The only real gap is how it relates to the sibling SMS tools, which an agent would need in order to route correctly.

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. Baseline 4 applies; the description correctly implies a no-input informational call.

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 makes clear this is a guidance tool: it 'Returns how to do it in AestheticsPro step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes the real behavior from what the name 'send SMS blast' implies. It stops short of naming a sibling tool as the alternative, so the boundary with e.g. aestheticspro_send_client_text or aestheticspro_schedule_e_blast is left implicit.

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 usable workflow: call this first to get the steps, then execute with cotlet_browser_* tools in the AestheticsPro Cloud Browser. It does not say when to choose this over the many neighboring SMS/text tools (send_client_text, schedule_e_blast, create_sms_template), nor does it give preconditions or exclusions.

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