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

The readOnlyHint=true annotation is reinforced and explained by "opens nothing by itself" — a genuinely useful disclosure because the tool name implies a write. It adds the reason (Nextdoor has no open API for Business Pages, checked 11 Oct 2026), which explains the instruction-only design. It stops short of describing the shape or length of the returned steps.

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 core behavior and the read-only guarantee. The phrase "from ChatGPT, Claude or any AI agent" is mild marketing filler that does not help an agent decide anything.

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?

For a zero-parameter, no-output-schema tool, the description covers what it returns (step-by-step instructions), what it does not do (opens nothing), and the handoff to the browser tools. Minor gap: no mention of prerequisites such as an authenticated 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 schema has zero parameters and 100% coverage, so the baseline of 4 is not reachable here because there is nothing for the description to add — but the description also does not explain that event details (date, location, title) will be gathered later via the browser tools, which would have closed the loop.

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 ("Create event in the user's own Nextdoor account") and immediately clarifies the crucial nuance that the tool returns instructions rather than performing the action. It does not explicitly contrast with sibling creation tools like nextdoor_create_post or nextdoor_create_for_sale_listing, which keeps it 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?

It states the follow-up path clearly: get the step-by-step screens/buttons/fields here, then execute with cotlet_browser_* tools in the user's Cloud Browser. That is real when/how guidance, though it never says when to prefer this over the other nextdoor_create_* siblings.

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