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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description reinforces this with 'opens nothing by itself' rather than contradicting it. It adds genuinely new behavior detail: the return value is procedural guidance with screens, buttons and fields, and the actual work must be done through the browser tool family. It omits prerequisites such as whether a Cloud Browser session or Wanderlog login must already exist.

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 sentences, front-loaded with the action and immediately followed by the crucial clarification of what is actually returned. The closing note about Wanderlog's lack of a public API earns its place by justifying why browser automation is required, though its phrasing ('Wanderlog's official API: Wanderlog has no public API') is slightly clumsy.

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 rich annotations, the description carries the right load: it explains what comes back and what must happen next. The main remaining gap is session/auth preconditions for the Cloud Browser step, which an agent would need before proceeding.

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 is 4. The description correctly implies no input is needed.

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 states a concrete resource (a booking in the user's Wanderlog account) and immediately corrects the misleading verb in the name: it returns step-by-step instructions rather than performing the import. An agent can tell this is a guide-producing tool, distinct from mutation siblings like wanderlog_create_trip. The opening sentence still reads as if the tool itself imports, which costs it a point.

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 an explicit workflow: call this to get screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Wanderlog Cloud Browser. It also rules out expecting any side effect ('opens nothing by itself'). It does not distinguish when to prefer this over wanderlog_add_place or cotlet_app_guide, so the sibling routing is incomplete.

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