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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds two genuinely new facts beyond that: the call is free and opens no browser session, and the result degrades gracefully to a general method for unknown apps. It does not describe the shape or length of the returned guidance.

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?

No sentence is filler, and the call-to-action timing appears early. However, the opening sentence is a long comma-chained list of guide contents that is hard to scan as a single run-on. Splitting the content inventory from the invocation rule would make it easier to parse.

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 only two optional parameters, no nested objects, and no output schema, the description carries the burden of describing the return value, and it does so by inventorying what the guide covers. The remaining gap is that nothing is said about output format or size, which matters mildly for an agent deciding whether to read the whole guide before acting.

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?

Schema coverage is 100%, so both parameters and their meanings are already documented in the schema, including the Wanderlog default. The description only implicitly confirms that arbitrary app names are acceptable. It says nothing about the `task` parameter, which affects how targeted the returned guidance is.

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 concrete resource and enumerates what the guide contains: browser choice for the workspace, sign-in link, step-by-step method, screens/menus/actions, notes, and app-specific tools. That is far more specific than the name alone, and it is clearly separable from the cotlet_browser_* siblings, which perform actions rather than explain them. It never says plainly that the tool returns instructional text, which keeps it just short of a 5.

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?

Timing is explicit: "Call it before the first browser step in an app." It also states the coverage condition, that any web app works and uncatalogued apps get the general method. It does not contrast itself with cotlet_apps, which is the nearest neighbor for app discovery, so routing between the two is left to inference.

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