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, so the safety profile is covered. The description adds meaningful context beyond them: it explicitly states the tool 'opens nothing by itself,' that its output is a step-by-step walkthrough, and that no official API exists, which prevents a wrong turn. Return format beyond 'step by step' is not described, keeping it short of a 5.

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?

Core capability and the no-side-effect caveat are front-loaded in the first two clauses, which is the right order. The closing sentence on Enterprise-plan pricing and a verification date is only loosely relevant and adds bulk, though it does justify why browser automation is required instead of an API call.

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 no parameters, no output schema, and strong annotations, the definition covers what the agent needs: what the tool produces, that it mutates nothing, and what tool to use next. A brief note on the structure of the returned steps (or that it is textual guidance only) would make it fully complete.

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 of 4 applies. The description correctly focuses on behavior rather than 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 names a specific verb and resource (export contacts to Constant Contact) and pins the scope to the user's own AestheticsPro account. It also draws a sharp line between this tool, which only returns instructions, and the cotlet_browser_* tools that actually perform the export, so an agent can tell what this tool is and is not.

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 clear sequencing guidance: run this first to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. It also rules out an API route by documenting that AestheticsPro publishes no public API docs or self-serve keys, which steers the agent away from a dead end. It does not name any sibling export/contact tool as an explicit alternative, leaving that inference to the agent.

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