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

The annotations declare readOnlyHint=true and idempotentHint=true, and the description is consistent with them: "opens nothing by itself" confirms no side effects occur. Beyond the annotations it discloses the return shape (screens, buttons, fields) and the prerequisite Cloud Browser dependency, which is genuinely additive. It omits whether the guide depends on account state or whether anything is logged, so a 4 rather than 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?

Front-loads what the tool does and what it returns, then the follow-up action, then the rationale for the guide approach. The final sentence is slightly clumsy and self-referential ("Wanderlog's official API: Wanderlog has no public API"), and the dated parenthetical adds friction without much value. Otherwise there is no 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?

With no parameters and no output schema, the description carries the burden of explaining the return value, and it does: a step-by-step walkthrough of screens, buttons, and fields. It also names the execution path via cotlet_browser_* and the Cloud Browser prerequisite. It does not sketch the shape of the returned steps or state whether the user must already be signed in, leaving a small gap.

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, which is the baseline-4 case. The description does not explain why a trip-creation guide needs no inputs (no trip name, destination, or dates), which is the one place it could have added meaning. Still, with an empty schema there are no parameter semantics to obscure.

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?

Names a specific verb and resource ("Create trip in the user's own Wanderlog account") and immediately clarifies that what is actually returned is a step-by-step guide rather than a completed creation. That clarification is essential because the name wanderlog_create_trip overpromises; with it, an agent understands the tool's real output. It stops short of 5 because the tension between the name and the actual behavior is resolved only by a subordinate clause, not stated up front.

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?

Explicitly routes the agent to the next step: do the real work "with the cotlet_browser_* tools in the user's Wanderlog Cloud Browser," which differentiates it from the browser mutation siblings. It also explains why no dedicated API path exists (no public API or developer docs). It does not state when NOT to use it, e.g. whether it applies only to the user's own account versus shared trips, so it falls short of a full when/when-not/alternative treatment.

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