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

Beyond the read-only annotations, the description explains that the tool returns step-by-step screens, buttons, and fields, opens nothing by itself, and requires follow-up browser tools. It also notes that Nextdoor has no open Business Page API, which is useful context for why the workflow is manual.

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 description is front-loaded with the core action and then explains the return behavior and next step. It is generally efficient, though phrases like 'from ChatGPT, Claude or any AI agent' are slightly promotional rather than operationally necessary.

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, read-only guidance tool with no output schema, the description gives everything an agent needs: what it returns, that it performs no action itself, and which tools to use afterward. The annotations already cover safety and idempotency, so no important context is missing.

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?

There are zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. The description correctly avoids inventing parameter details.

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 specific resource and scope: creating a post in the user's own Nextdoor account. It also clarifies the actual capability by saying the tool returns step-by-step guidance and opens nothing itself, which distinguishes it from the cotlet_browser_* action tools.

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?

The description gives a clear workflow: use this tool to get steps, then perform them with cotlet_browser_* tools in the user's Nextdoor Cloud Browser. It does not explicitly list when not to use it or name sibling alternatives such as nextdoor_create_event, but the resource-specific scope is clear.

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