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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces this with 'opens nothing by itself', which is exactly the clarification an agent needs to avoid assuming the text was sent. It additionally explains the return shape (step-by-step screens, buttons, fields) and why no direct API path exists, adding context the annotations cannot carry.

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 routing information is front-loaded, but the final sentence is a long digression about AestheticsPro's Enterprise pricing and the absence of public API docs, including an oddly specific check date. That rationale justifies the tool's existence but consumes roughly half the description and dilutes the operational instructions.

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 zero parameters and no output schema, the description needs only to say what comes back and what to do next; it does both by naming the returned content type and the cotlet_browser_* execution path. The only gap is that it never states what the agent should supply the user or the browser tools (e.g., recipient, message body) to complete the task.

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 no parameter semantics to document and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 procedural-guidance tool that returns step-by-step instructions (screens, buttons, fields) rather than performing a send, which distinguishes it from a real action tool. However, the lead sentence 'Send client text in the user's own AestheticsPro account' reads as an action verb and only the following clause corrects that impression, creating avoidable ambiguity about what the tool actually does.

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 the follow-up path explicitly: use the cotlet_browser_* tools in the user's AestheticsPro Cloud Browser to actually perform the send. It does not say when to prefer this over sibling capabilities like aestheticspro_send_sms_blast, aestheticspro_send_review_request, or aestheticspro_draft_client_communication_with_kai, nor any prerequisite such as the user having a browser session open.

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