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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds real value beyond them by stating it "opens nothing by itself," which tells the agent this is a pure guidance payload with no side effects. Beyond that it says nothing about what the returned guide looks like in structure or length.

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 behavior is front-loaded in the first two sentences, which is good. The closing sentence about Nextdoor's official API and Business Pages is tangential to listing recommendations and adds noise rather than decision-relevant information.

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 saying what comes back, and it does: "step by step (screens, buttons, fields)." Missing only prerequisites such as whether the user must already have a connected Nextdoor Cloud Browser session.

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 meaning to add; the schema baseline of 4 applies. No parameter claims in the description conflict with the empty object schema.

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 ("List recommendations in the user's own Nextdoor account") and immediately clarifies the non-obvious truth that the tool returns a step-by-step guide rather than the data itself. That resolves the mismatch between the name and the actual behavior, though it never contrasts the purpose with sibling tools such as nextdoor_get_page_stats.

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 explicit workflow guidance: this tool only tells you what to do, "then do it with the cotlet_browser_* tools in the user's Nextdoor Cloud Browser." That is a clear when-and-how. It stops short of naming when *not* to use it or which specific browser sibling to start with (navigate vs. open).

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